A bridge receipt needs proof on the destination chain

A cross-chain transfer touches 2 ledgers, so a successful source transaction alone does not prove your assets arrived. You need to match the transfer on the destination chain and confirm that the intended asset reached the intended address.

What does a completed bridge transfer mean?

A completed transfer means the destination chain recorded the delivery, not just that your wallet sent a transaction on the source chain. The bridge may first lock or burn tokens on one network, then arrange a corresponding release or mint on the other.

Those steps can happen at different times. A bridge interface may show that it has received your deposit while the destination transaction is still pending, or it may require a separate claim before funds appear in your wallet. For more on how a super bridge transfer handles custody and settlement, see the fuller explanation of that distinction.

“Sent,” “processing” and “received” are not interchangeable. Read the bridge’s status as a description of its process, then look for evidence on the destination chain before calling the transfer complete.

How do you check the source transaction?

Start with the transaction hash from your wallet or bridge page. A hash is the transaction’s unique identifier on one particular chain; it does not identify the whole cross-chain transfer by itself.

Open the source chain’s explorer and search that hash. Check that the transaction succeeded, that it interacted with the expected bridge or routing contract, and that the token and amount match what you intended to send. A failed transaction usually means the transfer did not begin, though the explorer may still show a network fee charged for the attempt.

Keep the source hash handy, but do not use its success status as the final receipt. The source explorer records activity on that network. It cannot confirm that a later transaction was included on another network.

How can you confirm the destination receipt?

Use the bridge’s tracking page or transfer details to find a destination transaction hash, if one is provided. Search that hash in the explorer for the destination chain, not the source chain.

Then check the destination transaction’s status and the details of what it changed. Confirm that the recipient is your intended address, the token is the asset you expected, and the amount is plausible after any stated fees or conversion. Token symbols can be reused across networks, so check the token contract or asset details when the explorer provides them.

If the bridge does not show a destination hash, check its transfer record for a clear status and instructions. Some routes require a claim or another action; in that case, follow the bridge’s stated process and verify the resulting transaction on the destination explorer. A wallet balance can help, but it may not refresh immediately or display an unfamiliar token automatically.

Use this sequence to check a transfer:

1. Copy the source transaction hash and open it in the source chain’s explorer.
2. Confirm the source transaction succeeded and its token, amount and destination details match your transfer.
3. Find the destination transaction or next required action in the bridge’s transfer record.
4. Check the destination explorer for a successful receipt to your address, with the expected asset and amount.

A transaction marked successful is included on its chain, but networks differ in how they handle finality: how settled a transaction is against the risk of later reversal. For a time-sensitive transfer, use the bridge’s instructions about when the source is ready for processing, then check the destination chain’s own status rather than assuming that one network’s confirmation settles both.

What should you do if the asset is missing?

First, check whether the destination transaction exists. If it is still pending or the bridge record says processing, the transfer may not have reached its final step yet. Give the route time to complete and check its status again.

If the destination transaction succeeded, compare the recipient address and token details with your intended transfer. A token may not appear in the wallet’s default asset list even when the chain recorded it; use the explorer’s transaction details to verify the receipt before taking further action.

If the source succeeded but no destination receipt appears, use the bridge’s official tracking or support route and provide the source hash. Avoid repeating the transfer until you know what happened to the first attempt. The useful proof is a matching record across both chains: the source event shows what left, and the destination event shows what arrived.