A cross-chain transfer can stay pending after your sending transaction succeeds because another step must confirm and deliver it on the destination chain. Check the transaction on both chains before acting: a successful send does not prove the tokens have arrived, and retrying too soon can create a second transfer.
Why can a transfer take longer than the first transaction?
A cross-chain transfer is a chain of transactions, not one instant move. The source chain records your send, a bridge mechanism verifies it, and a later transaction delivers or swaps the assets on the destination chain.
Think of it like a parcel that needs a dispatch receipt before another carrier can deliver it. A quiet interval between the receipt and delivery does not mean the parcel is lost. Different routes also use different checks, so there is no single wait time that applies to every transfer.
For example, Ethereum transactions are included in blocks and gain confidence as the chain confirms them. A bridge may wait for enough confirmation before acting. Ethereum.org explains how transactions move from pending to included and finalized; “finalized” means the block is very unlikely to be changed.
After that, a relayer—a service that carries verified messages between chains—or another bridge component may still need to submit the destination transaction. Rango Bridge is a cross-chain route service for moving or swapping tokens across networks; the route’s bridge mechanism determines what must happen between chains.
How can I tell which step is waiting?
Use the source transaction hash, a unique code for finding a transaction, to check the sending chain’s explorer. An explorer is a public site that shows on-chain activity. Look for whether the transaction is pending, failed, or successful.
If it failed, the transfer did not proceed as intended; read the failure reason before trying again. If it succeeded, note the destination chain and the receiving address from the transfer details. Then check that address on the destination chain’s explorer for the expected token.
No destination transaction yet usually means the handoff or delivery step is still pending. A destination transaction that failed is a different case: the bridge may have recorded the message, but the final action could not complete. Save both transaction hashes, if available, and compare the destination token and address with your original intent.
Some routes use Inter-Blockchain Communication (IBC), a protocol for passing messages between connected chains. The IBC Protocol specification describes how a relayer submits a packet and how the receiving chain can return an acknowledgement. That means the send can be complete while the message or acknowledgement still needs relaying.
What should I do while it is pending?
First, wait for the source transaction to reach the confirmation level required by the route. Then check the destination chain for a delivery transaction. If neither the status nor the destination balance changes, keep the hashes and wait for the route’s stated timeout or recovery guidance before taking another action.
Do not submit the same transfer again just because the destination balance looks unchanged. If the original delivery is merely delayed, a second send can move more tokens. Also check that the wallet is showing the destination network and the correct token; the same asset can have different names or representations across chains.
On-chain steps generally require network fees, often paid in that chain’s native token. A destination delivery can fail if it cannot pay the needed fee or execute the requested swap. Exact fees depend on the chains and route, so treat any estimate as route-specific rather than a fixed bridge charge.
When is it safe to try again?
Try again only after you have evidence that the first transfer failed, timed out, or was refunded. A timeout means the route’s allowed waiting period ended; on some systems, a separate transaction is needed to complete a refund. A pending label alone does not prove that the transfer timed out.
If the source transaction succeeded but the destination remains empty, check the route’s recovery instructions using the saved transaction details. Do not share your seed phrase or private key with anyone offering to “release” funds; those credentials give full control of your wallet.
Before starting another transfer with Rango Bridge or another cross-chain route service, confirm the destination chain, receiving address, token, and amount. The useful question to ask yourself is: Can I prove what happened to the first transfer before sending again?