You bridged your tokens an hour ago. The source transaction confirmed, but nothing has arrived on the destination chain. Your stomach drops. Before you assume the worst: delayed bridge transfers are common, and most resolve on their own. Here’s a calm, step-by-step recovery process.
Work through these steps in order — most “lost” bridge funds are found by step three.
id=”step-1-verify”>Step 1: Verify the Basics
First, confirm the source transaction actually succeeded: paste your transaction hash into the source chain’s block explorer (type the URL yourself). A successful bridge deposit shows your tokens leaving your wallet into the bridge contract. If that transaction failed or is still pending, nothing was ever sent — wait or retry.
Next, check the obvious: are you looking at the right wallet on the destination chain? Bridges often deliver a wrapped or differently-named token — you may need to add the token contract address manually to see your balance. Wrong network selected in your wallet is the #1 cause of “missing” funds.
Step 2: Track the Transfer Properly
Bridges publish transfer status. Find the bridge’s official explorer or status page (from a bookmark you made, or typed — never from a DM or ad) and paste your transaction hash. It will show whether your transfer is pending, in transit, or completed on the destination side.
Normal timeframes vary wildly: fast intent-based bridges take minutes, standard lock-and-mint bridges 10–30 minutes, and native L2 withdrawals can take days by design. If you’re within the normal window, waiting is the correct action. Our guide to bridge trust models explains why different bridges have different speeds.
Step 3: Escalate Carefully
If the transfer is well past its normal window and the explorer shows it stuck: check the bridge’s official status page or announcements for outages, then contact official support through the bridge’s own site or verified Discord — with your transaction hash ready. Never share private keys or seed phrases with anyone, including “support.”
Keep records: transaction hashes on both chains, timestamps, screenshots. If the bridge is custodial and unresponsive, these records are what you’d need for any formal complaint. And for next time: always send a small test amount first on any new route.
The Bottom Line
Bridge delays are usually benign: verify the source transaction, check the right network and token display, track the official status, then escalate through official channels. Patience plus verification resolves the vast majority of cases.
This guide is for education only — not financial advice.
