Five Checks for a Pending Cross-Chain Transfer

A pending cross-chain transfer may still be confirming on the source chain, waiting for a relayer, or ready for a step on the destination chain. The status label alone does not tell you which. Check the transaction on both chains and use the bridge’s tracker to see where the transfer stopped. For route and fee details, see this guide to bungee bridge. The checks below help you decide whether to wait, act, or seek support.

Did the source transaction land?

Start with the transaction hash from the wallet or bridge page, and open it in the source chain’s block explorer. Check whether it is pending, confirmed, or reverted. A confirmed transaction means the source chain recorded it; it does not mean the other chain has received the funds. The 0x cross-chain status guide makes the same distinction between an origin transaction and a completed bridge step.

If the transaction is still pending in the wallet, the bridge may not have started processing it. If it reverted, read the explorer’s error details before trying again. A replacement transaction or repeat transfer can create a second payment if the first one later lands.

Which step is still in progress?

Match the bridge tracker’s status to the transaction on the relevant chain. The tracker may show whether the source transaction is waiting for confirmation, the transfer is in flight, or delivery has completed. Status names differ between services, and some stages may pass too quickly to appear. The 0x guide notes that a status check can skip intermediate stages.

• Source pending: Check the source explorer and wallet before changing anything.
• Confirming: The bridge may be waiting for enough blocks to treat the source transaction as final. Chainlink’s CCIP documentation explains that finality rules and timing vary by chain.
• In flight: Compare the bridge’s status with its stated processing time. Congestion or the route’s own processing can add delay.
• Destination complete: Check the destination chain and the receiving address for the expected token.

A “complete” label can refer to a bridge step, not necessarily the balance shown in your wallet. Confirm the destination transaction and token contract on the destination explorer.

Does the destination need a separate action?

Check the tracker for a claim or receive step, and confirm the destination chain and address match your intended transfer. Some routes may require a separate destination transaction; if so, use the bridge’s own interface and verify the transaction details before signing. Also check the expected received amount and fees. A route that swaps tokens as it bridges may deliver a different asset or amount than the one sent.

If the source transaction is confirmed but the tracker has not advanced, save both the source hash and any destination hash shown. Use the bridge’s official support channel if the stated processing window has passed. Never share a recovery phrase or sign an unfamiliar transaction to “release” funds. The useful takeaway is simple: identify the stalled step first, then take only the action the route itself says is needed.