A pending bridge transfer usually needs time at one of two stages, depending on whether the source transaction is final. Check the source chain first; a wallet’s “sent” label does not mean the destination funds have arrived.
What does “pending” mean during a bridge transfer?
It usually means the transfer is waiting for the source chain to confirm the transaction, or for a cross-chain message to be processed and executed on the destination chain. A bridge message is the instruction that tells the destination what to release or swap.
Open the source transaction in that chain’s block explorer, a public page showing transaction records. If it is still pending there, the bridge may not have a confirmed transaction to act on. If it succeeded, note its transaction hash, a unique record ID, and check the bridge’s tracker for a separate destination status.
For example, if you send ETH from Ethereum to a layer 2, the source transaction can succeed before the destination transaction runs. Ethereum’s documentation explains that finality means a transaction is settled against reversal; bridge systems may then need additional time to verify and execute a message. Chainlink CCIP’s published message lifecycle describes these as separate source, verification, and destination steps. Other bridges can use different steps and timing.
How long should I wait, and should I send it again?
Wait until the bridge’s stated estimate has passed, then check both chains before taking action. There is no reliable single wait time: chain confirmation, network congestion, and the bridge’s verification and execution design all affect it.
If the source transaction succeeded, do not send the same amount again just because the destination is slow. A second transfer could arrive as a separate payment. With an acrossbridge crypto move and swap in one flow, check that the destination transaction has completed before treating the swapped asset as available to use.
If the source transaction failed, the bridge transfer generally cannot proceed from that transaction. Check the explorer for the failure reason and whether the wallet still shows the funds. A fee shortage or temporary network congestion can cause a failure; changing the amount or gas settings may be needed for a new attempt.
What should I check if the destination still shows nothing?
Compare the destination address and network in the transfer record with the wallet you are checking. Then search the destination explorer using the destination transaction hash, if one exists. A successful source transaction with no destination execution points to a delayed or failed bridge step, rather than proof that funds have arrived.
Also check which token arrived. A bridge may deliver a wrapped token, meaning a token that represents an asset from another chain, instead of the familiar version you held on the source chain. For an acrossbridge transfer that includes a swap, check the stated destination asset as well as the amount; the result can differ from the source token.
I would save the source hash, wait through the published estimate, and check the destination record before retrying. If the bridge marks the message failed, follow that bridge’s recovery instructions for the specific transaction.