If the source transaction succeeded but the tokens are missing, check the destination-chain record first; it tells you whether to wait or fix your wallet display. A Mantle bridge transfer can involve separate steps on the sending and receiving networks, so a success notice on the first one does not always mean the asset has arrived.
Check that you are looking at the right wallet and network
First, compare the receiving address in the transfer details with the address selected in your wallet. Wallet addresses usually start with “0x”; check the full address, since two accounts in the same wallet app can have different balances.
Next, switch the wallet to Mantle Mainnet. Its chain ID, the number that identifies a network to wallet software, is 5000. If you sent funds to another network, the asset will not appear in the Mantle balance.
Use the destination record to see if the transfer arrived
Search the receiving address on Mantle’s block explorer, a site that displays public network records. The official Mantle explorer is at explorer.mantle.xyz. Look for a token balance or an incoming transfer around the time your bridge route said to expect delivery.
For example, say you sent 0.2 ETH to your Mantle address. If the explorer shows an incoming transfer but your wallet shows no ETH, the network has recorded the receipt; the wallet may simply not display that token yet. If there is no incoming record, check the route’s status and destination details before taking another action.
A transfer may also include a swap, which trades one token for another. For a later move where you want to change assets too, fast Mantle bridge transfers can move and swap crypto across networks in one flow; check the expected output token when you compare the result.
Add the right token if the explorer shows your balance
If the balance appears on the explorer but not in your wallet, the wallet may not have the token’s contract address, the identifier for that token on Mantle. Import the address from the transfer details or a trusted source, and make sure you add it while Mantle Mainnet is selected.
Do not choose a token by ticker alone. Two tokens can share a short name, while their contract addresses differ. Check that the network and contract match the asset named in your transfer record before importing it.
Wait or get help if no destination record appears
A successful source transaction means the sending network accepted your instruction; the bridge still has to complete its part. Some routes take longer than others, so compare the route status with its stated time before deciding the transfer is stuck.
If that time has passed and no destination record appears, keep the source transaction hash, a public receipt number for the transfer, and contact the route provider through its official site. Do not send the transfer again just because your balance looks unchanged, and never share your recovery phrase or private key.
In your place, I would check the address, network, and destination record in that order. If the explorer confirms the balance, I would import the verified token contract; if it does not, I would use the transaction hash to ask the route provider what remains to complete.
Top comments (0)