A bridge transaction stuck in “pending” is usually delayed, not lost. Start with the source-chain transaction hash: if it failed or never confirmed, your funds never left. If it confirmed, look the hash up on the bridge’s own explorer to see whether the message is waiting for attestation, a relayer, or a manual claim. Many “missing” transfers have actually arrived and only need the token added to your wallet. Work through the five checks below in order, and never accept help from anyone who messages you first.
Key takeaways
- Find the source transaction hash first; every diagnosis starts there.
- Each bridge family has its own tracker: LayerZero Scan, Wormholescan, Axelarscan, the LI.FI and Socket explorers, or the rollup’s bridge UI.
- Withdrawals from optimistic rollups need a prove step, a waiting period and a finalize step; skipping one leaves funds parked.
- Intent bridges refund automatically on the origin chain if no relayer fills your order.
- Unsolicited “recovery” offers are scams; report them to the FBI’s IC3 and the FTC.
Step zero: get the transaction hash
Open your wallet’s activity tab, find the bridge transaction, and copy its hash (a long string starting with 0x on EVM chains, or a base58 signature on Solana). Then paste it into the source chain’s block explorer: Etherscan for Ethereum, Arbiscan for Arbitrum, Basescan for Base, Solscan for Solana and so on. What you see there decides your next step.
Bridge transaction stuck: the five-stage triage
Stage 1: the source transaction is pending or failed
Symptoms: the explorer shows “pending”, “dropped” or “failed”, or cannot find the hash at all.
What it means: nothing has been bridged. A pending EVM transaction is usually waiting because the gas price was set too low. A failed one reverted, and your tokens stayed in your wallet minus the gas spent.
Fix: in wallets that support it, use “speed up” to resubmit with higher gas, or “cancel” to replace it with a zero-value transaction using the same nonce. If it failed, read the error on the explorer (often slippage, an expired quote, or insufficient approval) and request a fresh quote.
Stage 2: confirmed on the source, waiting on the bridge
Symptoms: the source transaction succeeded, but nothing has arrived after the time the bridge estimated.
What it means: the bridge’s off-chain layer is still working. Messaging bridges wait for source-chain finality and verifier signatures. Circle’s CCTP waits for an attestation, which Circle’s docs put at roughly 15 to 19 minutes for standard transfers from Ethereum and Ethereum L2s, and much longer from some chains (Linea standard transfers can take many hours). Intent bridges wait for a relayer to fill.
Fix: look the hash up on the bridge’s explorer (table below). If it shows “inflight”, “confirming” or “waiting for attestation”, wait. If it shows “failed” or “blocked” on the destination side, the explorer usually offers a retry or a manual execution button.
Stage 3: a canonical withdrawal waiting to be proved or claimed
Symptoms: you withdrew from an L2 back to Ethereum using the official bridge and see nothing on mainnet days later.
What it means: withdrawals from optimistic rollups are not delivered automatically. OP Stack chains generally require you to submit a prove transaction once the withdrawal is included in a posted state root, wait out the challenge window (seven days on OP Mainnet), then submit a finalize transaction. Arbitrum withdrawals wait roughly a week and then need a claim on Ethereum. Base changed its proof system in 2026 and quotes shorter windows in its docs. Each extra step costs mainnet gas.
Fix: return to the official bridge interface you used, connect the same wallet, and open the transactions or withdrawals tab. It will show “ready to prove” or “ready to claim” when the next step is available. Funds wait indefinitely; they do not expire.
Stage 4: arrived, but your wallet does not show it
Symptoms: the bridge explorer says “delivered”, but your balance looks unchanged.
What it means: this is the single most common “stuck” case. Your wallet may be on the wrong network, or it does not display that token by default.
Fix:
- Switch your wallet to the destination network.
- Open the destination transaction from the bridge explorer and click through to the destination chain explorer. Note the token contract that was sent to you.
- In your wallet, use “import token” or “add custom token” and paste that contract address. Get the address from the explorer or the token issuer’s official site, never from a search result or a chat.
- Check whether you received a wrapped or bridged variant (for example USDC.e instead of native USDC). It is still your money, but it may need a swap to become the token you wanted.
Stage 5: delivered to the wrong place
Symptoms: the explorer shows delivery to an address you do not recognise, or to the correct address on a network your wallet does not use.
What it means: on EVM chains, the same address exists on every network, so funds sent to your address on a “wrong” EVM chain are usually recoverable by adding that network to your wallet. Funds sent to a typo, a token contract, or an exchange deposit address on an unsupported network are much harder. Our explainer on what a wallet address is covers why formats differ between chains.
Fix: if it went to an exchange, open a ticket through the exchange’s official site with the hash. If it went to a smart contract wallet that only exists on one chain, contact the wallet provider’s official support. If it went to a stranger’s address, it is likely gone.
How to track a bridge transaction: explorers by protocol
| If your route used… | Track it on | What to look for |
|---|---|---|
| LayerZero (including many OFT tokens such as USDT0) | LayerZero Scan | Status of source, verification and destination delivery |
| Wormhole (Portal and Wormhole-based apps) | Wormholescan | Whether the guardian signature (VAA) exists and whether it was redeemed on the destination |
| Axelar or Squid | Axelarscan | Gas paid, approved, executed; options to add gas if underpaid |
| Circle CCTP | The app you used, or a CCTP-aware explorer | Whether the attestation is complete and the mint executed |
| LI.FI / Jumper or Bungee | The LI.FI explorer or Socketscan | Which underlying bridge handled each step, plus links to its explorer |
| Canonical rollup bridges | The official bridge UI’s transaction history | Prove, claim or finalize prompts |
If you used an aggregator, its explorer is the starting point because it tells you which bridge actually moved the funds.
Stuck bridge refund: how intent bridges handle unfilled orders
Intent bridges such as Across and Relay rely on relayers to fill your order on the destination chain. If no one fills it, you are refunded on the origin chain:
- Across: an unfilled deposit expires after its fill deadline, and the refund is executed after Across’s settlement process. Its documentation warns refunds can take several hours, so do not panic at the one-hour mark.
- Relay: its docs describe automatic refunds to the origin chain when a fill fails, usually close to instantly, with the gas for the refund deducted from the amount.
Other bridges have similar mechanisms; check their docs or the status shown on their explorer before contacting support.
Contacting bridge support safely
- Find support links only on the bridge’s official website or documentation, reached from a bookmark.
- Prepare the source hash, both chains, the token, the amount and the time sent.
- Use the official ticket form or the official Discord’s ticket system, never direct messages.
- Real support staff will never ask for your seed phrase, private key, or for you to “validate” or “sync” your wallet on a website, and will not ask you to send funds to unlock a transfer.
Recovery services are scams
When people post about a stuck transfer on social media, fake support accounts and “fund recovery” services reply within minutes. They ask for a seed phrase, a “fee” or remote access to your device. Paying them loses more money. Our guide to crypto scam recovery explains how these schemes work. If you are targeted or have lost money to one, report it to the FBI’s Internet Crime Complaint Center (IC3) and the Federal Trade Commission in the US, or your national fraud agency elsewhere.
A genuine stuck transfer is resolved by the bridge’s own system, the canonical claim process, or the bridge’s official support. To reduce the chance of a repeat, the guide to bridging crypto covers choosing routes, and the bridge safety guide covers the risks. More walkthroughs are in the crypto bridging hub.
FAQ
Why are my bridged tokens not showing?
Usually because your wallet is set to a different network or does not list the token automatically. Check the destination transaction on the bridge’s explorer, note the token contract you received, switch your wallet to that network and import the token by contract address. Also confirm whether you received a bridged variant rather than the native token.
How long can a bridge stay pending?
It depends on the design. Intent bridges usually fill in seconds to minutes; CCTP standard transfers from Ethereum take about 15 to 19 minutes; some routes depend on slow finality and take hours. Canonical withdrawals from optimistic rollups wait days and then need a manual claim. Compare elapsed time with the bridge’s own estimate before worrying.
What if my bridge transaction was not received after a day?
Look up the hash on the bridge’s explorer. If it shows delivered, import the token. If it shows a failed destination execution, use the explorer’s retry option or contact official support. If it is a canonical L2 withdrawal, check whether it is waiting for a prove, finalize or claim step.
Can a stuck bridge transaction be cancelled?
Only before it confirms on the source chain, by replacing it with a higher-gas cancel transaction using the same nonce. Once confirmed, the bridge controls the next steps, and the outcome is either delivery or the bridge’s refund process. Intent bridges refund automatically if unfilled.
Crypto is volatile and risky; this is education, not financial advice. Do your own research.
