Find Where Your Cross-Chain Transfer Is Stuck

You diagnose a pending cross-chain transfer by finding the stage where its status stops advancing. A confirmed source transaction means the sending chain accepted the transaction; it does not prove the bridge has delivered funds to the destination.

Why is my cross-chain transfer still pending?

A transfer usually passes through several stages: the source transaction is submitted, the bridge or its relayers observe it, and a destination transaction releases or mints the corresponding asset. A delay can happen between any two stages, and different bridges use different designs, so a wallet’s single “pending” label may hide the part that needs attention. For a fuller account of a stuck transfer involving manta bridge, see the linked guide. The key is to compare the source transaction with the bridge’s own status and the destination chain’s records.

How can I tell which stage has stalled?

Trace the transfer in order, using the transaction hash and the networks and token you selected. Start with the source chain’s explorer: if the transaction is unconfirmed, the bridge cannot process it yet; if it failed, check the wallet or explorer for the reason. If it succeeded, look for that transaction in the bridge’s status page, then check the destination explorer for a release or mint.

1. Copy the source transaction hash from your wallet’s activity.
2. Search that hash on the source chain’s explorer and confirm whether it succeeded or failed.
3. If it succeeded, enter the hash in the bridge’s status tool and note the last completed stage.
4. Search the destination explorer for the receiving address or destination transaction, then compare the asset and amount.

These records help distinguish a slow transfer from a failed one. A source success with no bridge update points to a later stage; a destination transaction that failed is different from a transfer that has not arrived.

What should I do before retrying?

Use the last recorded stage to choose your next step. A useful status check is whether the source transaction succeeded, whether the bridge observed it, and whether a destination transaction exists. If the source transaction failed, resolve that failure before submitting again. If the source succeeded but the bridge has no matching record, check that you used the right bridge interface and networks. If the bridge reports completion, verify the destination address and token display; a token may not appear in a wallet until it is added there.

Do not repeat a transfer just because the destination wallet looks empty: first confirm whether the original transaction succeeded and whether the bridge has already processed it. The transaction hash and the last completed stage give you a clearer basis for action than the word “pending” alone.