Why Is My Cross-Chain Transfer Still Pending?
If you have sent tokens from your own wallet and they have not appeared on the destination chain, check the transfer’s stage before taking action. A bridge transfer can involve more than one transaction, so a confirmed source transaction does not always mean the destination payment is complete.
A bridge transfer moves through several stages
A cross-chain transfer is a sequence of actions recorded on separate blockchains, rather than one transaction that travels between them. The bridge has to observe what happened on the source chain, verify or relay that information, then make the destination action happen.
Depending on the route, the bridge may lock tokens on one chain and mint a representation on the other, burn tokens before minting them elsewhere, or use a liquidity provider to send tokens on the destination chain. Ethereum.org describes these as distinct bridge designs; the steps and waiting times therefore vary by route.
For a typical transfer, think of the status in these stages:
- Submitted: Your wallet sent a transaction, but the source chain has not confirmed it yet.
- Source confirmed: The source chain recorded the transaction; the bridge may still need to verify it or wait for the required confirmations.
- Destination processing: A relayer, bridge contract, or liquidity provider is completing the transfer on the other chain.
- Complete or claimable: The destination transaction has succeeded, or the route requires you to submit a final claim.
A route may skip a visible claim step, but the stages still help explain why a transfer can be “pending” after your wallet says “confirmed.” A failed destination action can also leave a transfer requiring a retry or claim, rather than another source transfer.
Use the source transaction hash to find the stuck stage
Start with the transaction hash in your wallet’s activity, then open the explorer for the source network and search that hash. Check whether the transaction succeeded, failed, or is still waiting, and confirm that its token amount and destination address match what you intended.
If it succeeded, open the route’s transfer history or status tool and search using the same hash. It should show whether the message has been relayed, whether the destination transaction was submitted, and whether a manual action is available. Then check the destination chain’s explorer; a confirmed destination transaction can exist even if your wallet is still showing the source network.
For example, Arbitrum’s bridge instructions say an Ethereum-to-Arbitrum deposit typically takes around 15–30 minutes, while an Arbitrum-to-Ethereum withdrawal through its native bridge has a seven-day waiting period before it can be claimed. Those timings apply to that bridge and direction, not to every route. The difference is a useful reminder to check the specific route’s expected time before treating a wait as a fault.
Check the destination network, token, and claim step
If the destination transaction succeeded but you cannot see the funds, switch your wallet to the destination network and check the exact address that received them. Some wallets hide tokens until you add the correct token contract; a token with the same ticker can also be a different asset from the one you expected.
On a route that needs a claim, use the route’s own transaction history and follow its prompt only after confirming the transaction hash and destination. Arbitrum, for instance, keeps withdrawal status in its bridge transaction history and offers a claim when a withdrawal is ready. A claim is a separate destination-side action, so it may require gas in the destination chain’s native token.
Super Bridge brings together routes from native bridges and third-party providers, so a transfer made through it still follows the selected provider’s settlement process. Keep the source hash, route details, and destination address together when you check status; the aggregator’s quote alone cannot tell you whether a provider has completed a later on-chain step.
Choose the next action based on the status
Once you know the stage, take only the action that stage calls for. If the source transaction failed, no successful transfer began; review the failure in the source explorer and correct the cause before trying again. If it is pending on the source chain, wait for that chain to confirm or replace the transaction using your wallet’s controls if it is still eligible.
If the source succeeded but the route is still processing, use the route’s status page or its official support channel with the transaction hash. Do not send the same amount again just because the balance has not appeared: the first transfer may still complete, leaving you with two transfers. If the route marks the destination transaction as failed or claimable, follow its recovery steps and check whether a claim or retry needs destination gas.
For a cross-chain transfer, “confirmed” may describe only the source transaction. Check the source hash, track the route’s later steps, and verify the destination token and address before acting. When the status says claimable, complete that step; when it says processing, give the route its stated time before escalating.
Comments
Post a Comment