A confirmed source transaction can still be waiting for delivery on the other chain. The transfer usually passes through several stages, so “confirmed” does not always mean the destination asset has arrived.
A confirmed source transaction is only the first stage
Confirmation means the first blockchain recorded your transaction. The bridge may still need to wait until that record is final, meaning the chain considers it very unlikely to be reversed.
- Source confirmation records the transaction.
- Finality lets the bridge safely act on it.
- Destination execution delivers or swaps the asset.
These stages explain why a wallet can show spent funds while the destination balance has not changed. For example, say a route waits for 20 blocks, and each block takes about two seconds. The bridge may need roughly 40 seconds before it can start its next step; actual waits depend on the chain and route.
After finality, the bridge’s relay carries the transfer details to the destination chain. A relay is the service that passes this information between chains. The destination transaction then needs to be included in a block before the asset appears.
The status tells you where the wait is happening
Check the transaction record on both chains, using the source transaction hash to find its progress. A hash is the transaction’s unique reference code. Look for a destination transaction or a status that says the bridge is still processing the transfer.
If the source transaction is pending or failed, the bridge may not have received a completed transfer to process. If it is confirmed but not final, wait for the route’s required confirmations. If it is final and still processing, the delay is likely in verification, relay, or destination execution.
A bridge-and-swap can also have a later step: converting the arriving asset into a destination token. For example, what ParaSwap does when gas is missing explains why source confirmation alone may not complete that destination swap.
Wait, retry, or recover based on the destination record
If the bridge shows the transfer is still processing, avoid sending it again. A second transfer is a separate transaction and could move more funds while the first one is still on its way. Check the route’s stated status and allow time for its current stage to finish.
If there is a destination transaction, inspect whether it succeeded or failed. A failed destination swap does not always mean the source transfer failed too; the asset may have arrived without being converted, or the route may offer a recovery path. The exact outcome depends on how that bridge handles failed execution.
If the source is final but no destination transaction appears after the route’s stated processing window, keep the source hash and check the route’s own transaction record. ParaSwap combines bridging and swapping across chains in one flow, which can help when the goal is to move funds and receive a different destination asset. Use its recorded status to decide whether to keep waiting or follow the available recovery steps.