A pending cross-chain transfer may still be moving between networks. First check whether the source transaction succeeded, then find out if the destination step is still waiting.
A transfer can involve more than one on-chain action: your source transaction, checks by the bridge protocol, and a destination transaction. For how a Bungee bridge handles treasury transfers, see the full treasury walkthrough; here, the focus is working out what to do when a transfer stalls.
Open the source transaction hash in that network’s block explorer. A hash is the transaction’s unique reference, and the explorer shows whether the network accepted it.
If it is still pending, the source chain has not included it in a block yet. Wait for the wallet or network to resolve it. Don’t start another bridge transfer just because the destination balance has not changed.
If the transaction failed or reverted, the bridge call did not complete. You may still have paid the source chain’s gas fee, which is the network cost for processing a transaction. Check the explorer’s error details before trying again.
If it succeeded, record the source and destination networks, token, amount, recipient address, and transaction hash. These details help you match the transfer to a status record or explorer entry.
A successful source transaction does not always mean the destination tokens have arrived. The route may still be waiting for source-chain confirmation, cross-chain message verification, or a transaction on the destination chain.
For example, imagine you send USDC from Ethereum to Base using a route that also swaps tokens. The Ethereum transaction can succeed first, while a later message or swap remains unfinished. Check the route’s status using the original source hash, then compare it with the source and destination explorers.
Ethereum.org describes a transaction’s path from broadcast to block inclusion and, later, finality. Finality means the block is considered settled and very unlikely to change. Cross-chain routes can wait for that confidence before continuing, so a wallet’s “success” label may describe only the source step.
Retry only the step that failed, and only through instructions for the protocol used by your route. Some messaging protocols separate verification from execution. LayerZero’s documentation, for example, says a verified message whose destination execution failed can sometimes be retried without sending the source transaction again.
That recovery method is protocol-specific. A Bungee bridge aggregator can route transfers through different protocols, so one route’s retry or refund process may not apply to another. Check the route details and the protocol’s own guidance before signing a new transaction or paying destination-chain gas.
If the source transaction succeeded and the route still appears pending, keep its hash and check for a destination transaction or a protocol-specific recovery option. If the destination transaction failed, use its error details to identify whether the route supports a retry, refund, or claim.