How to Check If a Cross-Chain Transfer Is Stuck

A cross-chain transfer is stuck only when it has stopped progressing beyond the route’s expected time, and the source transaction succeeded. Check the source and destination transactions separately: a wallet balance that has not changed does not show which stage is waiting or whether the transfer failed.

A transfer is complete only after the destination transaction succeeds

Moving assets between chains is like sending a parcel through a depot: the sender’s receipt proves it left, but only the delivery record proves it arrived. A bridge may need to observe the source transaction, wait for it to become final, and then submit a transaction on the destination chain.

For a relay bridge, relayer nodes carry information about the source event so it can be acted on elsewhere. The route may also use a liquidity pool, which can affect when funds are available. A displayed “confirmed” status may refer only to the source chain, so look for a destination transaction or a clear final status.

Check each stage before taking action

Use these checks in order; each one narrows down where the delay is happening.

1. Open the transfer details and copy the source transaction hash. A hash is the transaction’s unique ID. Check it in the source chain’s block explorer, the public site that shows transaction records, and confirm it says “success,” not “pending” or “failed.”
2. Compare the elapsed time with the route’s estimate. Wait through the stated estimate, which can vary with chain congestion, required confirmations, and bridge processing. If the estimate is around 10 minutes, for example, that is a guide rather than a guarantee; a busy chain can take longer.
3. Look for a destination transaction hash or status update. If the source succeeded but no destination transaction appears after the estimate, check the bridge’s status page or support instructions. A crypto relay bridge handles a message between chains, so checking both sides helps identify whether the source is waiting for finality or the destination submission is delayed.
4. Check the destination address and token display. Confirm the transfer used your intended wallet address on the destination chain. If the destination transaction succeeded but the token is missing in your wallet, check that the wallet is viewing the correct chain and displaying that token.
5. Contact the bridge’s support team if the route remains unresolved. Provide the source hash, destination chain, wallet address, and transfer time. Do not submit the same transfer again until you know the first one failed or the bridge explains how retries work.

In short, a missing balance is a symptom, not a diagnosis. Confirm the source result, check the route’s expected time, then use the destination record to decide what to do next.