just did bridge from iotx to bsc with iotx token
just did bridge from iotx to bsc with iotx token but i have not received yet
from this address
0xd7020700fd2a7bbc9609d35073333172467691b1
on this address
0x3e76381f8559ea3c4683cd0433231ca0fb69498b please help
Log in to comment and vote
Comments2
mentor your
Oct 26, 2025
here txn status
https://iotexscan.io/tx/0x5e746ac8ab8cd6b6149ada476cec71ab1274cecff53cc3d39fe8c830d44295ab
Precy R
Oct 27, 2025
I understand this is a stressful situation. Let's troubleshoot the bridge transaction step by step. When you bridge tokens, they don't appear automatically - you need to add the correct token address on the destination network.
1: Verify the Transaction First Before anything else, let's confirm the bridge transaction actually processed:
Find your transaction hash:
Go to iotexscan.io
Paste your IoTeX wallet address Step
Look for the "bridge out" transaction and copy the Transaction Hash
Check bridge status:
Visit the official IoTeX Bridge: https://bridge.iotex.io/
Connect your wallet (make sure it's on IoTeX network)
Check the "Transaction History" or "Recent Transactions" section
Step 2: Add BSC Network to MetaMask (If Not Already) Your tokens are on Binance Smart Chain, so you need to be connected to BSC:
Go to: chainlist.org
Search for "Binance Smart Chain"
Click "Connect Wallet" and then "Add to MetaMask"
Or manually add:
Network Name: BSC Mainnet
RPC URL: https://bsc-dataseed.binance.org/
Chain ID: 56
Currency Symbol: BNB
Block Explorer: https://bscscan.com
Step 3: Add IOTX-e Token on BSC This is the most common issue - people don't add the correct token contract:
Switch to BSC network in MetaMask
Click "Import tokens"
Use this official IOTX-e contract address on BSC: text 0x9678E42ceBEb63F23197D726B29b1CB20d0064E5
The token symbol (IOTX) and decimals should auto-populate
Click "Add Custom Token"
You should now see your bridged IOTX balance.
Step 4: If Still Missing - Check These If the tokens still don't appear:
Check BSCScan:
Go to bscscan.com
Paste your wallet address
Look under "Token Holdings" for IOTX
Common delays:
Bridges can take 5-30 minutes during high traffic
BSC might require several block confirmations
Verify you used the official bridge:
There are fake/scam bridges - ensure you used https://bridge.iotex.io/
Important Reminder:
Never share your seed phrase/private key with anyone
Official support will NEVER DM you first asking for sensitive information
Double-check you're using the official bridge and correct contract addresses
Try these steps in order, and in most cases, the issue is simply needing to add the correct IOTX token contract on the BSC network. I hope this helps to clarify and if you have further query please don’t hesitate.