A bridge transfer can look stuck because its source transaction and destination credit happen in separate steps, and a successful source transaction does not prove the funds have arrived. Check the transaction on the chain it was sent from first, then trace whether the route completed on the destination chain before you retry.
A bridge transfer has separate source and destination stages
A cross-chain transfer is a message between two networks, not one transaction shared by both. Your wallet signs a transaction on the source chain; after that chain records it, the bridge route must make the corresponding asset available on the destination chain.
Think of it like checking a suitcase onto a connecting flight: the first airport can confirm it departed while the destination airport has not yet logged its arrival. Some routes rely on a relayer or verifier to pass a message between chains; others use liquidity already available on the destination, then settle the difference later. Those designs have different timing and status labels.
A bridge that also swaps assets adds another stage: the route may need to exchange the source asset for the destination asset before crediting your wallet. For a Mantle bridge transfer, a source-chain confirmation and a Mantle balance update are separate pieces of evidence. An app may show one status for the whole route, but the block explorers show what happened on each chain.
The source transaction tells you whether the transfer began
Find the source transaction hash in your wallet’s activity and open it in the explorer for the network you sent from. Confirm the sender address, token, amount, and transaction status. A transaction marked “pending” has not yet been included in a block; one marked “failed” was included but its action reverted.
If it is pending, the cause may be a low gas fee or an earlier transaction from the same wallet that is still waiting. EVM wallets assign transactions a sequential nonce, so a pending transaction with a lower nonce can hold later ones behind it. Use your wallet’s replacement or speed-up option only if you understand which transaction it will replace; a replacement with the same nonce may supersede the original.
If the source transaction succeeded, record its hash and check the bridge route’s status using that hash or the route’s own tracking reference. Do not send the same amount again just because the destination balance has not changed yet. The first transfer may still be processing, and a second one could create a second transfer.
Destination checks reveal where the delay is
Check the destination explorer for the receiving address and the exact asset expected from the route. Make sure the wallet is displaying the destination network: a token balance on Mantle will not appear in the Ethereum view, even when the address is the same.
A successful source transaction followed by no destination transaction usually means the cross-chain stage is still underway, or the route has not completed. If the destination transaction exists but failed, inspect its result and token contract: the intended asset may differ from a similarly named token, or the route may have encountered a destination-side execution error. If the transaction succeeded but the balance is invisible, check the token’s contract address and decimals in the destination explorer before concluding that funds are missing.
When the transfer includes a swap, compare the destination asset and amount with the route’s quoted output, allowing for market movement and any stated slippage tolerance. A swap can fail even after the source-chain transaction succeeded; those are different outcomes. For a route that moves and swaps assets across chains in one flow, a Mantle bridge swap service can handle that combined task, while you should still verify the source transaction and final destination balance independently.
Route type determines what “complete” means
Completion depends on the bridge mechanism. A liquidity route may deliver the destination asset after its own checks, while a canonical rollup withdrawal can have additional proof and challenge stages before funds become available on Ethereum. A long wait during a withdrawal is not automatically a stuck transfer; compare the route’s current stage with the process it uses.
For the canonical Mantle bridge, a deposit from Ethereum and a withdrawal back to Ethereum do not have identical timing. Deposits can require the Ethereum transaction to be confirmed and then relayed to Mantle. Withdrawals may require a proof and a challenge period before finalization, so do not assume the delay for one direction applies to the other.
The practical next step is to keep the source hash, identify the route and direction, and check both chain explorers for the same wallet address and asset. If the source succeeded but the route has no destination result after its stated processing window, use the route’s official status or recovery process with those transaction details; never share your recovery phrase to get help.
Top comments (0)