Seeing "waiting for target transaction" simply means your cross-chain operation got stuck halfway. The money has already left your wallet, and the source chain fee has been deducted, but the target chain has not finished confirming yet. Your funds are most likely not lost. They are sitting in the bridge contract on the target chain, waiting for target chain nodes to complete verification.
A leading global cryptocurrency platform,suitable for both beginners and experienced traders.
New user benefit: 20% off trading fees upon registration!！
A cross-chain transfer is not one transaction. It is a combination of two transactions: a source chain transaction plus a target chain transaction. When you see "waiting for target transaction," it means the source chain side has already been confirmed. The asset is locked in the bridge contract and is waiting for the target chain's verification nodes to handle the second half and release the asset to your target address.
Step 1: Confirm the status — is it really stuck or just queued?
[What to do]: Tell the difference between normal delay and an abnormal stuck state.
[How to do it]: Open your wallet transaction history and find the full hash value (TxID) of this transfer. Copy it into the corresponding source chain block explorer to check the status. If it shows "Success", it means the source chain has indeed confirmed it, and the problem is on the target chain side. In that case, move to the next step. If the status is "Pending", it means even the source chain has not been confirmed yet. The gas fee may have been set too low, so either keep waiting or use an acceleration tool.
[Completion standard]: You can see the source chain transaction status as "Success" in the block explorer, with a sufficient number of block confirmations.
Step 2: Check the target chain confirmation process
If the source chain has already succeeded, the problem usually lies in one of the following areas. Check them in order:
Checkpoint 1: Not enough gas fee on the target chain
When the bridge releases assets on the target chain, it also needs to pay the target chain gas fee. If your target address does not have enough of the corresponding network's native token — for example, Arbitrum requires ETH, BSC requires BNB, and Polygon requires MATIC — the bridge contract cannot complete the target chain transaction and will remain stuck in the "waiting for target transaction" state. This is one of the most common causes.
Checkpoint 2: Target chain node congestion or synchronization delay
The bridge needs to wait for target chain nodes to complete verification and reach consensus. This process can take anywhere from a few minutes to several dozen minutes. If the target chain network itself is congested, confirmation time will be extended. This is not your fault. You can only wait for it to finish processing.
Checkpoint 3: The receiving address's chain type and network do not match
This mistake ranks near the top of common errors. For example, the target address you entered is technically correct, but it is an Ethereum address, while the target chain you selected is BSC. The address format may look the same, but the chain is wrong. The asset will enter the bridge contract and get stuck. It can be found on-chain, but it will never show up in your wallet. This error is basically irreversible and requires contacting the wallet or the official bridge customer service for help.
A leading global cryptocurrency platform,suitable for both beginners and experienced traders.
New user benefit: 20% off trading fees upon registration!！
Step 3: After the normal waiting window passes, check the target chain explorer
The target chain confirmation time of a bridge depends on the bridge protocol and the network conditions on both ends. Generally, the waiting time ranges from a few minutes to several dozen minutes, and it may be longer during peak periods.
[What to do]: Proactively check whether this pending transaction exists on the target chain.
[How to do it]: Open the block explorer for the target chain. For example, if you are transferring to BSC, use BscScan. If you are transferring to Polygon, use PolygonScan. Enter your target wallet address and check whether there is an incoming transaction marked "pending" or "processing." If the issue is caused by gas fees, some explorers may show a warning. If the explorer shows this pending transaction, it means the funds are already on the target chain but have not been finally confirmed. If the explorer shows no record at all, it means the bridge has not yet started the target chain confirmation step. In that case, you need to wait or contact customer service.
[Completion standard]: You can confirm the status of this transaction in the target chain explorer, or confirm that it truly does not appear on-chain.
Risk reminder: When you find a cross-chain transaction stuck, do not submit the same cross-chain transaction again. Submitting it again will cause two transactions of the same amount to be pending at the same time, tying up your funds. You will also have to pay gas fees twice on both sides, and it will not speed up the confirmation of the original transaction. The correct approach is to check the status, identify the cause, and handle it in a targeted way, rather than "just try again and see."
