Bridge Transfer Stuck or Tokens Not Arrived? How to Track and Recover Cross-Chain Funds

Most bridge transfers that look lost are in one of four states: the source transaction failed, the bridge is still verifying or relaying the message, the transfer is waiting for you to claim it (common on rollup-to-Ethereum withdrawals, which can take days), or the tokens have arrived but your wallet is not showing that network or token. As of October 2026, check them in that order using the transaction hash: the source-chain explorer, then the bridge's own explorer, then your address on the destination-chain explorer. Funds are generally unrecoverable mainly when they were sent to an address you do not control or over a route the bridge does not support; a bridge exploit or a manual transfer left unclaimed past its deadline can also mean a loss, so do not leave a claim pending.

Where are your funds right now? The four states of a missing bridge transfer

A missing bridge transfer is almost always in one of four states, and only block explorers, not a wallet or dApp label, can tell you which. A transfer is a source transaction (lock, burn or deposit), a verification and relay step, and a destination transaction (mint, release or fill), sometimes followed by a claim.

A "pending" label in a wallet or dApp is not proof of anything. For the procedure itself, see how to bridge crypto across chains.

Step 1: Did the source transaction actually succeed?

Copy the transaction hash from your wallet's activity list, then open it on the source chain's explorer: the status field tells you whether the bridge ever received your tokens.

• Success: continue to Step 2.
• Failed or Reverted: the tokens never left your address and you only lost the gas. You can retry.
• Pending: the transaction is still waiting to be included, usually a network-fee or mempool problem, not a bridge problem.
• Not found: check that you are on the right chain's explorer and copied the full hash; the transaction may also have been dropped or replaced.

Also confirm that the "To" address is the bridge contract you meant. See how to read the status field on a block explorer.

Step 2: Look the transfer up in the bridge's own explorer or status page

Most bridges and messaging protocols publish an explorer that accepts your transaction hash or address and shows which side the transfer is stuck on.

LayerZero Scan is one example. Its documented statuses include Inflight (waiting for confirmations, verification or execution), Delivered, Payload Stored (the message arrived but reverted or ran out of gas and needs a retry) and Blocked (an earlier message with a stored payload is halting this one). Range's July 2026 guide lists common causes of an "in flight" transfer: finality or attestation delays, relayer backlogs and destination liquidity shortfalls. Most resolve without any action from you.

Decision rule: if the bridge explorer says delivered or completed, go to Step 3. If it says failed or needs a retry, use the bridge's official app or support channel. Never use a link someone sends you in a message.

Step 3: Check your address on the destination chain explorer

Search your own receiving address, not the transaction hash, on the destination chain's explorer and open its token transfers tab. If the incoming transfer is listed, your funds are on-chain and the problem is display only, so go to Step 5. If nothing is there, check that the receiving address is the one you intended, because some bridge interfaces let you enter a different recipient.

Step 4: Does the transfer need a manual claim or finalisation?

Withdrawals from optimistic rollups to Ethereum through the native bridge are not automatic: you complete them yourself after a waiting period.

• OP Mainnet: a withdrawal is three transactions (initiate on L2, prove on L1, finalise on L1), and the Optimism docs give a 7-day challenge period on mainnet before finalisation.
• Base: follows the same three-step flow. Base's documentation states a 5-day finalisation window on the standard path and 1 day on a dual-proof fast path, down from 7 days, so check its current figures.
• Arbitrum: per the Arbitrum bridge docs, withdrawals from Arbitrum One or Nova to Ethereum take at least seven days, after which you press Claim.
• Message-based bridges: some routes need a redeem transaction on the destination chain. Wormhole's documentation describes both a manual route and an automatic relayer route.
• Intent-based bridges: a relayer fronts funds on the destination chain. On Across, if no relayer fills a deposit before its deadline, the refund goes through settlement bundles and, per the Across docs, takes several hours rather than minutes.

A claim is itself a transaction, so you need a way to pay fees on the chain where you submit it.

Step 5: Funds arrived but your wallet shows nothing

If the destination explorer shows the transfer, the funds exist and your wallet is simply not displaying them.

1. Switch networks. Hyperlane's help center (January 2026) notes that wallets do not automatically switch to the destination network after bridging.
2. Import the token. Newer tokens are often not auto-detected. Copy the contract address from the official bridge docs, or from the incoming-transfer entry on your own address page on the destination explorer; never from a token-name search result or a chat. See how to add a custom network and token to your wallet.
3. Check the contract. A lock-and-mint bridge may deliver a wrapped version, not the canonical token, and OFT-based stablecoins such as USDT0 mint a token at a specific contract on each chain. See omnichain vs wrapped and bridged tokens.
4. Wait and refresh. Wallet interfaces can lag behind the chain; the explorer is the reference.

If balances are still missing on a chain your wallet supports, other reasons a wallet balance does not show covers indexer and RPC causes.

When are bridged funds actually lost, and how do you avoid fake support?

Bridged funds are genuinely lost mainly when they were sent to an address you do not control or over a route the bridge does not support, according to Range's July 2026 guide; a bridge exploit, or a manual transfer left unclaimed past its deadline, can also end in a loss. Aurora's help article (last updated 2022) says the same and adds that tokens from a failed transfer can be accessed only from your own wallet. If you sent to the right address but the wrong network, read what to do when you sent crypto to the wrong network.

Fake support is the other real risk, because scammers message people who post that their funds are stuck. Real support never asks for your seed phrase or private key, never asks you to validate or sync your wallet on a website, and should not start a private chat with you out of the blue; if you opened a ticket, reply only inside that ticket. See how to spot crypto phishing.

When you contact official support through the link on the bridge's own website, bring only public data: the source transaction hash, the source and destination chains, the token and amount, your receiving address and the bridge explorer link.

How WATS Wallet relates to bridge troubleshooting

WATS Wallet does not change how bridge tracking works: the checks above apply to a transfer made from any wallet. WATS Wallet, made by Alltoscan LLC, is a non-custodial wallet (a Chrome extension and an iOS and Android app) with built-in swap and bridge across EVM networks, Solana and TON. WATS never holds a key, so it cannot reverse, speed up or retrieve a bridge transfer.

One narrow point: on EVM networks WATS Wallet charges every action's fee in ATS through an ERC-4337 paymaster, debited from one ATS balance held on BSC whichever EVM network you use. If bridged tokens land on an EVM chain where you hold none of its native gas coin, you can still move them on or send a follow-up transaction, as long as that ATS balance covers the fee. You never bridge ATS and keep no per-chain ATS balance. The ATS fee tracks the live network cost, so it is not a discount. Fees on TON are paid in ATS too, while Solana transactions pay their own fees in SOL. Details are in how ATS fees work on EVM networks.