It has been several hours since you made the transfer. The source chain shows the transaction was successful, but the funds still have not appeared in your destination chain wallet. The first time this happens, it is easy to panic.
The world's largest cryptocurrency exchange by trading volume,leading in security and liquidity.
New user benefit: Enjoy 20% off trading fees upon registration!
Do not worry. In most cases, your money is not lost. It is simply still on the way. The cross-chain transfer process is more complex than you might think. As long as you follow the steps below to troubleshoot, you will most likely find the cause.
Step 1: Confirm the transaction was successful on the source chain first
This is the most basic and most important step. Many "slow arrival" problems are actually caused by the source chain transaction not being completed yet.
[What to do]: Confirm that the funds have actually left your source chain wallet and have been confirmed by the blockchain network.
[How to do it]:
Open the wallet app you used for the transfer, such as the Binance App or MetaMask, and go to your transaction history.
Find this cross-chain transfer record, click to view details, and copy the "Transaction Hash (TxID)".
Open the blockchain explorer for the source chain. For example, use Etherscan if you transferred from Ethereum, or BscScan if you transferred from BSC. Paste the transaction hash into the search bar.
Case A: The explorer shows the transaction status as "Success" and the number of confirmations is large enough, usually more than 10.
What this means: Your funds have left the source chain and been safely handed over to the cross-chain bridge system. This step is fine, and the problem is in a later stage.
Case B: The explorer shows the status as "Pending" or "Fail".
What this means: The funds have not actually been transferred out. This may be because the gas fee you set was too low, so the transaction is still waiting in the mempool. It may also be because of network congestion. You need to resolve this source chain transaction first, for example by using the wallet's "Speed Up" function to increase the gas fee and try again.
[Completion standard]: Confirm on the blockchain explorer that the source chain transaction status is "Success".
Step 2: Check the destination chain to confirm whether the assets have reached the "ready to claim" state
If the source chain transaction is confirmed successful, then the funds are in the cross-chain bridge system. In many cases, the final step of a cross-chain transfer requires you to manually "claim" the funds on the destination chain. The system will not automatically complete it for you.
[What to do]: Check the cross-chain bridge page to see whether you need to manually complete the final step.
[How to do it]:
Go back to the page where you initiated the cross-chain transfer, such as the bridge interface in the Binance Web3 Wallet.
Carefully observe the page status. After the source chain transaction is confirmed, many bridges will show a "Claim", "Complete", or "Retry" button on the page.
Case A: You find a "Claim" or "Complete" button.
What this means: The assets are already prepared on the destination chain, but you need to click confirm yourself to complete the final minting or transfer. Click it and pay a small gas fee on the destination chain to receive the funds.
Case B: The page shows "Waiting for block confirmation" or "In progress".
What this means: The bridge validators are still confirming your source chain transaction or preparing assets on the destination chain. This usually takes anywhere from a few minutes to several hours, especially when the network is congested.
[Completion standard]: The bridge page shows "Completed", or your destination chain wallet balance has been updated.
Step 3: Check whether your destination chain wallet has enough "toll fee"
This is a pitfall that beginners easily overlook, and it is also the most common reason why the final step fails.
[What to do]: Confirm that your destination chain wallet has enough native tokens to pay the gas fee.
[How to do it]:
Open your destination chain wallet. For example, if you are bridging to BSC, check your BSC wallet address. Check whether your wallet has the native token of that chain, such as:
Bridging to BSC requires BNB
Bridging to Polygon requires MATIC
Bridging to Arbitrum requires ETH
If the balance of these native tokens in your wallet shows "0" or is insufficient, you will not be able to pay the gas fee needed to "claim" the assets or complete the final transfer, which will cause the transfer to get stuck.
[Completion standard]: Your destination chain wallet has enough native token balance to pay for one or two normal transactions.
Common failure causes and troubleshooting
Cause 1: The destination chain is congested: Just like the source chain, if the transaction volume on the destination chain suddenly surges, or if a popular project is launching tokens, your transaction may need to wait in the mempool, and processing time will be significantly longer. Solution: The main thing is to wait patiently. Congestion can last for several hours during peak periods.
Cause 2: Wrong chain or address selected: In cross-chain transfers, choosing the correct network is a matter of life and death for your funds. If you transfer assets from BSC to an Ethereum address, the assets will enter a contract that no one controls and will be extremely difficult to recover. Platforms like Binance show network selection prompts on deposit pages. It is recommended to enable the "network smart prompt" feature. If you find that you selected the wrong chain, please stop any further operations immediately and contact official customer support.
Cause 3: The bridge itself is congested: When a large number of users use the same bridge at the same time, its processing capacity reaches its limit, causing delays. This is especially common during periods of high market volatility. Solution: Again, wait patiently. It is usually processed within 24 to 48 hours.
Risk reminder: If the source chain transaction shows success but the funds still have not arrived after more than 2 to 3 days, do not repeatedly initiate cross-chain operations, and do not try to use another bridge to "chase" the funds. This will make the problem more complicated and may even cause asset loss. You should prepare your transaction hash (TxID) and contact Binance customer support through official channels.
The world's largest cryptocurrency exchange by trading volume,leading in security and liquidity.
New user benefit: Enjoy 20% off trading fees upon registration!
FAQ
Question: The transfer has been stuck for a long time. Can I close the page or turn off my device? Answer: Yes. The status of a cross-chain transaction is recorded by the blockchain network and has nothing to do with whether your device is online. Closing the page will not affect the transaction process. You can rest and check back after a few hours.
Question: It has not arrived for a long time. Could the money be lost? Answer: Most likely not. As long as you see the source chain transaction shows "Success" on the block explorer, your funds are in the cross-chain bridge system. They may just be stuck in the "queuing" or "waiting to be claimed" stage.
Question: How do I know when a long wait becomes "abnormal"? Answer: A simple rule of thumb: Not arrived within a few hours is normal; around 1 day, keep waiting; 2 to 3 days, consider contacting customer support; more than 3 days, prepare your transaction hash and submit a support ticket.
