Pending or stuck? Check each stage of a cross-chain transfer

A cross-chain transfer is pending while its source transaction awaits confirmation, and still in flight when the source has completed but the destination step has not. Check the source transaction hash first, then follow the bridge’s status and the destination chain’s record before deciding whether anything is stuck. A wallet’s “pending” label alone does not show which stage is waiting.

How do I tell whether the source transaction is pending?

Open the transaction hash in an explorer for the source chain named in the transfer. Ethereum.org’s bridge guide describes cross-chain movement as activity across separate networks; the source explorer can show whether the first transaction was included, reverted or is still waiting.

If there is no receipt yet, the bridge may not have received the transfer. If the transaction reverted, check the explorer’s error details and the bridge’s instructions before trying again. A wallet showing a submitted transaction is not proof that the bridge step began.

What does pending mean after the source transaction confirms?

After source confirmation, a bridge may still need to verify the deposit, obtain a message or attestation, find destination liquidity, or submit a transaction on the destination chain. These steps vary by route. Socket’s Bungee documentation describes status tracking across source and destination transactions, while 0x’s status guide distinguishes an origin transaction from a bridge that is still in flight.

For route mechanics and the delays they can create, see how Bungee Bridge routes transfers. The Bungee name refers to a routing interface; the selected route and its bridge determine which processing steps apply.

Use the bridge’s own transaction tracker, if it provides one, and match the source hash, destination chain and recipient address. Treat a status such as “bridge pending” as evidence that the transfer is being processed, not as proof that it has failed. Status labels differ between providers, and a tracker can lag behind on-chain activity.

What should I check before calling a transfer stuck?

Look for the destination transaction hash in the bridge tracker, then open it on the destination chain’s explorer. A confirmed destination transaction to the intended address is the clearest evidence of delivery; if no destination hash appears, the bridge may still be processing the route or may require a separate action.

• Confirm the source hash belongs to the wallet and chain used for the transfer.
• Check whether the source transaction succeeded, reverted or remains unconfirmed.
• Compare the tracker’s latest status with the destination explorer and recipient address.
• Read the route’s official instructions for any retry, claim or refund step.

Do not submit the same transfer again just because a status label has not changed; that can create a second transaction and another fee. Use the bridge’s official support channel if its tracker reports a failure or gives no usable next step, and never share a recovery phrase to get help.

The next useful signal is a destination transaction, a changed bridge status, or an official recovery instruction. Until one appears, whether a confirmed source transfer will complete, need a claim, or be refunded remains unconfirmed.