A cross-chain transfer can confirm and still be stuck

To tell if a cross-chain transfer is stuck, check its source transaction on the sending chain, then look for a matching destination transaction or status in the bridge’s tracker. A successful source transaction proves the sending step completed; it does not prove the bridge finished delivering funds. That distinction helps you avoid paying to send the same transfer twice while the first one is still moving.

What does a confirmed source transaction tell you?

It tells you the sending chain accepted the transaction, not that the destination chain has received the asset. Open the transaction hash in the sending chain’s block explorer and check whether its status is successful or failed. If it failed or reverted, the intended bridge action usually did not complete, though the network fee may still have been charged.

If it succeeded, find the bridge or route tracker using the transaction hash, wallet address or transfer ID. The next step may involve waiting for source-chain confirmations, bridge verification, a relayer, available destination liquidity or a transaction executing on the receiving chain. For a closer look at where those steps can pause, see this Biswap guide to stalled routes.

How can you locate the step that is waiting?

Compare the route tracker with the explorers for both chains. A source transaction that succeeded, followed by no destination transaction, points to a delay or failure after the send; a destination transaction that failed means delivery was attempted but did not finish as intended. Status labels vary by bridge, so use the tracker’s explanation and transaction records together.

• Source pending: The sending-chain transaction has not confirmed. Check the explorer before deciding whether a wallet replacement or cancellation is available.
• Source successful, bridge pending: The send is recorded, but verification or relaying may still be in progress.
• Destination transaction pending: The receiving-chain transaction has been submitted but has not completed.
• Destination successful: Check the receiving wallet’s address, selected network and token list; the asset may not appear under the name or token address you expected.

Each extra step can add time and, depending on the route, another fee. Some routes also require the recipient to have the destination chain’s native token to use or move the delivered asset. Check the route’s quoted costs and instructions before starting a transfer, and keep both transaction hashes for support.

When should you wait, retry or contact support?

Wait when the route tracker shows an active step and the relevant chain has not reported an error. A busy network or a bridge’s confirmation requirements can make the elapsed time longer than the wallet’s initial estimate. The expected duration depends on the chains and bridge design, so compare the transfer with that route’s stated estimate rather than treating every delay as a lost transfer.

Do not submit the same transfer again simply because the destination balance has not changed: the original may still complete. If the tracker shows a failed step, has stopped updating beyond its stated window, or reports that action is needed, follow the bridge’s recovery instructions or contact its support with the source hash, route and destination address. Never share a seed phrase or sign an unrelated transaction to “release” funds.