How to Confirm a Cross-Chain Transfer Arrived
A cross-chain transfer is complete when the destination network records the expected tokens in your wallet, not when the sending transaction merely succeeds. Check the source transaction, wait for the route to deliver its message, then verify the destination balance and token. If the route requires a claim, complete that step before calling it done.
A transfer finishes in two stages
First, the source network must accept your transaction. Then the bridge route must carry the transfer information to the destination network, where tokens are released or created for you. Ethereum.org describes common bridge designs that lock tokens on one network and mint equivalent tokens on another.
These steps can have separate records. A successful source transaction proves that the first step happened; it does not prove that the destination step finished. Some routes also wait for the source transaction to reach finality, meaning it is settled enough that the network is unlikely to reverse it.
The wait depends on the source network’s settlement rules, the route’s processing, and activity on the destination. The Ethereum Improvement Proposal for cross-chain messaging describes source and destination gateways as separate parts of a message transfer. That helps explain why a route can show progress after the sending transaction is already done.
Follow the transaction record to the destination
Start with the source transaction hash, the unique ID shown by your wallet or transfer screen. Open it in the source network’s block explorer, a site that lists transactions, and check that it succeeded and sent the intended token and amount to the route.
Then return to the transfer screen and open its status details. Look for a destination transaction hash or a message status such as “delivered.” If your case uses an aggregator that selects among bridge providers, Super Bridge is a concrete example of why the route’s final delivery status matters alongside the first transaction.
Check the destination network and wallet address before judging the result. A token may arrive under a different display name or contract address, so compare the token details shown for that route. If the destination explorer shows no transaction yet, the transfer may still be waiting for processing.
Choose the next step from the status
If the source transaction failed, the transfer did not start successfully. Read the wallet’s error and check whether the source network charged a fee; a failed transaction can still use network fees. Fix the cause before trying again.
If the source succeeded but the destination is pending, do not send the same transfer again just because the screen is slow. Check the route’s stated time estimate and status updates. Network congestion or a wait for finality can extend delivery, and a second transfer could send your tokens twice.
If the route says “claim,” it usually needs one more destination transaction signed by you. Read the wallet prompt, check that it names the expected destination network and action, and keep enough of that network’s native token for any fee. Afterward, confirm the destination transaction succeeded and the balance changed.
What if the source says success but nothing arrived?
Save the source transaction hash and check the route status before contacting support through the service’s official site or app. If the route offers a recovery or claim step, follow its instructions and verify the destination address first. Never share your recovery phrase or approve an unrelated transaction to “unstick” a transfer.
How do I know I received the right token?
Compare the destination token’s name, contract address, and amount with the details shown for your chosen route. A familiar ticker alone is not enough, because different tokens can use the same ticker. If the explorer shows delivery but your wallet balance does not, refresh the wallet or add the token’s verified contract address.