A slow cross-chain transfer is usually waiting on one of its steps. First check whether your wallet sent the source transaction, then follow the route’s status to the destination. Don’t send the same amount again while the first transfer is still pending; you could pay twice.
What does “pending” mean at each step?
A cross-chain transfer can involve several steps, so “pending” does not always mean your tokens are lost. The source transaction is the first payment your wallet sends on the network where your tokens start.
After that transaction is confirmed, the bridge service must carry out its part. Depending on the route, it may wait for enough source-chain confirmations, then send a message or transaction to the destination network. Confirmations are records added after a transaction; some routes wait for several to reduce the chance of a reversal.
For a transfer assembled across available routes, a bungee bridge can help select a route, while the source transaction hash shows whether funds left your wallet. A transaction hash is the unique code for a transaction. Save it from your wallet or transfer screen before checking anything else.
How can you find which step is delayed?
Use the transaction hash to check the source network’s block explorer, a public page that shows network transactions. Search the hash and look for its status. If it says failed, the transfer did not complete on that network; if it says pending, the network has not confirmed it yet.
If the source transaction is confirmed, return to the transfer service’s status page and check for a destination transaction hash. A confirmed destination transaction means the transfer reached the destination network. If the service shows no destination hash yet, its route may still be waiting or processing the cross-chain message.
Check the destination wallet on the correct network, too. A common mistake is looking for tokens on the starting network or in a wallet view that hides that token. The fix is to switch the wallet to the destination network and check the token balance there. A token can arrive without appearing in the wallet’s default list.
What should you do if it stays stuck?
Use the route’s status page or support instructions before taking another action. The wait depends on the networks, confirmation rules, and route; a busy network can take longer. A transfer that has a confirmed source transaction but no destination result needs a different check from one still pending at the source.
If the status page offers a recovery action, read what it does before signing. A signature approves an action from your wallet. Some routes may offer a way to complete a delayed step, while others require waiting or contacting support with the source hash. Never share your recovery phrase or private key; neither is needed to look up a transaction.
Once the destination transaction is confirmed, check that the received token and amount match the transfer details. A bungee bridge route can involve a token swap, which exchanges one token for another, so the destination amount may differ from the amount sent. In your place, I’d save both transaction hashes and confirm the destination balance before trying again.