Cross-Chain Bridge Shows Complete But Funds Haven't Arrived: How Long Does It Usually Take
Cross-chain bridges may show complete but funds haven't arrived—usually it takes anywhere from a few minutes to several hours, depending on which step is stuck.
Cross-chain transfers are different from regular transfers. It's not a direct send from Chain A to Chain B, but rather two separate steps: "send funds to the bridge → the bridge releases funds to the destination chain." The "complete" you see may only mean the first step—the source chain has confirmed it—while the release on the destination chain hasn't been triggered yet.
Prerequisites
The transaction hash (TXID) of the source chain transaction.
The wallet address on the destination chain (verify it matches the address you entered during the cross-chain transfer).
A small amount of the native token (ETH/BNB/MATIC, etc.) reserved for gas fees on the destination chain.
Step 1: Check Transaction Status Using the TXID First
Don't keep refreshing your wallet—use a block explorer for the most accurate information. Paste the TXID into the block explorers for both the source chain and the destination chain.
What Different Transaction Statuses Mean
Scenario A: The source chain shows Success, but the destination chain shows no record of this transaction. Funds have left your account but haven't entered the destination chain yet. This is the most common delay stage—the cross-chain bridge is queuing for settlement.
Scenario B: Both the source chain and destination chain show Success, but your wallet doesn't display the funds. This means the assets have already arrived on the destination chain, but your wallet isn't switched to the correct network, or you haven't added the token's contract address.
Scenario C: The source chain transaction still shows Pending. The transaction hasn't been confirmed on-chain at all. In this case, use your wallet's "Speed Up" function to increase the gas fee.
Completion standard: Identify which of the three stages your transaction is in—source chain Pending, source chain confirmed but destination chain hasn't received, or destination chain received but not displayed.
Step 2: Estimated Wait Time by Stage
| Current Stage | Typical Wait Time | Recommended Action |
|---|---|---|
| Source chain Pending | Depends on network congestion—could be minutes to several tens of minutes | Use wallet's "Speed Up" function to increase gas fee |
| Source chain confirmed, destination chain not received | Most cross-chain bridges take 1-3 minutes; 30 minutes to 1 hour during congestion | Wait patiently; do not repeat the operation |
| Destination chain received but wallet not displaying | 0 minutes (already arrived) | Switch wallet network, add the token |
Special case: The Arbitrum official bridge requires an 8-day challenge period when withdrawing from L2 to L1. This is by design, not a malfunction.
Completion standard: You can estimate how much longer your transaction needs to wait or confirm whether manual action is required.
Step 3: Check If There Are Enough Gas Fees on the Destination Chain
Many people overlook this step. If you're bridging to a new chain and your destination chain address has zero native tokens for gas, the assets can't trigger the final "claim" or "arrival" step even once they arrive. The result: the bridge side keeps waiting for your confirmation, leaving things stuck halfway.
What to do: Check your address balance on the destination chain block explorer. If the native token balance is zero, first send a small amount (e.g., 0.01 ETH/BNB/MATIC) of the native token to this address, then go back to the cross-chain bridge interface to see if there's a "Claim" or "Retry" button—click it to complete the final step.
Completion standard: The destination chain address has sufficient gas, and the cross-chain bridge interface has no pending claim buttons.
Step 4: How Long Before You Should Contact Customer Support
Different timeframes call for different responses:
Not arrived after a few hours: Normal—this is common when cross-chain networks are congested.
Around 1 day: Keep waiting, but start preparing screenshots and the TXID.
2-3 days: Reach out to the official customer support of the cross-chain bridge. Note: Contact the support team of the specific bridge you used (e.g., Across, Hop), not your wallet's support.
Common Reasons for Failure
Seeing a "Complete" notification and assuming everything is done—when in reality, the cross-chain bridge may still require you to click a "Claim" or "Complete" button on its interface before assets are actually released to the destination chain. Staring only at your wallet without checking the bridge interface can cause you to miss this step.
Risk warning: During a cross-chain delay, do not do the following: repeatedly submit the same cross-chain transfer, try another bridge to cross-chain the same funds again "just to test," send tokens directly to contract addresses, or switch wallets or networks without understanding the current status. These actions can turn what was merely a slow process into a tangled mess—and even cause real asset loss. Anyone asking for your private key or seed phrase under the pretext of "helping speed up your stuck cross-chain transaction" is absolutely a scammer.
Verification Method After Completion
Enter your address into the destination chain's block explorer—if your balance has increased, the funds have definitively arrived. If the cross-chain bridge interface has a "Transaction History" or "Status Inquiry" feature, use that first to confirm.
Next step after arrival: It's recommended to initiate a small test transaction on the destination chain first to verify that the address can sign and broadcast normally. If the cross-chain asset is a bridged version of a token, be aware that it may differ from the native token in price and liquidity. From "showing complete" to final arrival, most cases are resolved within 30 minutes; if the network is congested, it may take several hours.
