Why Your Cross-Chain Transfer Is Still Pending

Your source-chain transaction can be confirmed while your cross-chain transfer still shows pending. The transfer needs another step on the destination chain, and that step can take time or fail even after the first transaction is complete.

What does pending mean on a cross-chain transfer?

Pending means the bridge has not recorded the transfer as complete; it does not, by itself, tell you where the process stopped. The source transaction may still be waiting for confirmation, the bridge may be waiting for enough source-chain finality, or a relayer may not yet have submitted the message to the destination. Some designs also wait for a destination transaction to execute or for you to claim the funds.

These stages matter because a bridge coordinates two separate chains, each with its own block production and fees. A relay bridge uses a relayer to carry a message between chains; the linked explainer covers that arrangement and its costs in more detail. Other bridges use different verification and settlement methods, so the same status label can refer to different steps.

How can you tell where the transfer is stuck?

Start with the transaction hash from the bridge page, then check the source chain’s explorer. If the transaction is missing, unconfirmed, or reverted, the source step has not completed successfully. If it succeeded, look for a destination transaction or message record in the bridge’s own tracker or the destination chain’s explorer. No destination record may mean the transfer is still awaiting finality, relay, or processing; a failed destination transaction points to a different issue.

Use the bridge’s status tracker alongside the chain explorers, since a wallet balance or a single “pending” label may not show every stage. Check that you selected the intended destination network and address, and look for a claim instruction only if the bridge identifies one for your transfer.

What should you do if it stays pending?

Follow the transaction through these checks before taking another action:

1. Confirm whether the source transaction succeeded or reverted.
2. Use the bridge tracker to identify the last completed step and check its official status updates.
3. If the source succeeded but the destination step is absent or failed, contact the bridge’s support with the transaction hash and ask whether the transfer needs a claim, retry, or protocol-specific recovery.

Do not submit a second transfer just because the first one is pending; you could send the funds twice. A refund is not automatic in every bridge: some protocols allow one after a timeout, while others require a specific recovery process. Treat the bridge’s documented status and instructions as the guide for your particular transfer.