A Mantle bridge transfer can take time because the sending chain must confirm it, then a bridge or service must deliver it to the other chain. The stages depend on the route, so first check where the transfer stopped. Knowing how a Mantle bridge moves assets helps you tell a transfer apart from a token approval, which only gives permission to spend tokens.
Check the sending transaction before anything else
- Find the transaction hash in your wallet’s activity.
- Open it in the explorer for the chain you sent from.
- Check whether it succeeded, failed, or is still pending.
- If it succeeded, check the destination chain and address.
A transaction hash is a public record number for one action. An explorer is a website that shows those public records. Use the explorer for the sending network first; a Mantle transaction will not appear in an Ethereum explorer, or the other way around.
If the record says “pending,” the sending chain has not finished processing it. Wait for confirmation before trying again. If it says “failed” or “reverted,” the transfer did not complete on that chain; check the wallet’s error details before starting over.
A successful record is a good sign, but it does not always mean the destination balance has arrived. The route may still need to relay a message or complete a separate destination transaction. Ethereum.org explains that bridges can use different methods to move assets, so the steps and timing vary by route.
Match the destination details and wait for delivery
Check that the receiving address is the one you intended and that your wallet is set to the destination network. Then look for the destination transaction or balance. A token can arrive under a different contract address; a contract address is the token’s unique identifier on that network. Search by the verified token contract if the balance is missing.
For example, if you sent USDC from Ethereum to Mantle, first confirm the Ethereum transaction. Then check your address on Mantle and look for the delivered USDC there. An approval record alone is not a transfer: it permits a contract to use tokens, but does not send them. This distinction often explains why an early wallet record appears without a destination balance.
There is no single wait time for every route. Source-chain congestion, confirmation rules, and destination processing all affect delivery. If the source transaction succeeded but the destination remains empty well beyond the route’s estimate, use the route’s transaction record or status information before taking another action. Do not resend a confirmed transfer just because the balance has not appeared.
For a later move that also changes assets, mantlebridge.us lets you move and swap crypto across different blockchains in one flow. Before your next transfer, keep the source transaction hash and verify the destination network and address.