A pending bridge transfer usually needs a stage check before a retry. A cross-chain transfer has separate steps: the source chain records your transaction, a bridge or route processes it, and the destination chain records the result. The right next move depends on which step has stopped.
A Mantle bridge moves supported assets between Mantle and another network, so checking both chains helps you tell a slow transfer from a failed one. Start with the source transaction hash—the identifier shown by your wallet or service—and open it in the source chain’s explorer. For a Mantle bridge transfer, the same rule applies: a wallet showing “pending” does not tell you whether the source transaction, cross-chain processing, or destination delivery is pending.
Is the source transaction still pending?
If the source explorer has no confirmed transaction, the transfer has not yet reached the bridge’s processing stage. It may be waiting for the network to include it in a block, often because the transaction’s gas price is low relative to current demand or the network is busy.
Check the transaction’s status and confirmation count before doing anything else. If it remains pending, wait or use your wallet’s replace or speed-up function if available; that usually submits a replacement using the same account nonce. Don’t send a second transfer just because the first is slow: if both transactions eventually confirm, you may pay for two transfers.
For example, if the route says it needs 15 source confirmations and the explorer shows 11, four remain. At an observed average of 2.5 seconds per block, that is roughly 10 seconds of block time, though congestion and the bridge’s own processing can add more.
Has the source confirmed, but the destination is empty?
If the source transaction is confirmed, the bridge can still be waiting to verify or execute the cross-chain message. A message is the record that tells the destination side which transfer to complete; some routes process it automatically, while others rely on a separate relayer or validator process.
Use the source hash to check whether the route reports the transfer as completed, processing, or failed, and look for a destination transaction hash if one is provided. Then check the destination explorer and confirm that your wallet is set to the intended network and address. A token can arrive at the right address but remain invisible in a wallet until that token is displayed there.
This option is best when the source transaction succeeded and the route still shows work in progress. It does not fit a source transaction marked failed: a bridge cannot complete a transfer that never successfully entered its process. Avoid submitting again while the original message is processing, since that can create a duplicate transfer.
Does the source transaction show “failed”?
A failed source transaction means the chain included it but did not execute the requested operation. Open the transaction details and check the receipt status: 0 means execution failed; 1 means it succeeded. The wallet may show an error, but the receipt is the decisive check.
Failed transactions can still consume network gas, because validators processed them even though the requested transfer did not complete. Read the explorer’s error or revert reason if available. Common causes include an expired authorization, insufficient token allowance, or a contract condition that was not met; fix the stated cause before attempting the transfer again.
This path is for a confirmed transaction with a failed receipt. It does not fit a successful receipt followed by a missing destination asset. In that case, check the route’s processing status first rather than paying to repeat the source transaction.
What if the route says complete, but you received nothing?
If the route marks the transfer complete, check the destination transaction and its recipient address. A successful destination receipt confirms execution, but verify that the address matches yours and that the asset is the expected token; a token with a similar name may not be the same asset.
Keep the source hash, destination hash, asset, amount, and recipient address together when tracing the transfer. If there is no destination hash or the route still reports processing, the destination step may not have finished. If the destination receipt succeeded but the balance is missing, check the wallet’s selected network and token display before retrying.
Next, identify the first stage that lacks a successful receipt: source transaction, cross-chain processing, or destination execution. Act on that stage, and retry only when the evidence shows the original transfer failed or never began.
Top comments (0)