How to Confirm a Cross-Chain Transfer From Your Wallet

To confirm a cross-chain transfer, check both the transaction on the sending network and the result on the receiving network. A wallet’s “sent” message usually confirms only that the first transaction was submitted; the bridge may still need to process it and complete a separate action on the destination chain.

A transfer can involve two separate transactions

A cross-chain transfer moves an asset between networks through a bridge, so its progress is recorded on more than one chain. Depending on the bridge, it may lock or burn the asset on the source network, then release or create a corresponding asset on the destination; a relayer or other messaging system may carry the instruction between them.

That handoff explains why one transaction hash may not tell the whole story. If you’re moving funds from Ethereum to Mantle, a Mantle bridge transfer is a concrete example: first the source transaction must succeed, then the destination side must execute before the funds appear in your Mantle wallet. The wait between those events depends on the route’s design and the networks involved.

Before sending, note the source and destination networks, token, amount, and receiving wallet address. Keep the source transaction hash, a unique identifier for that on-chain transaction, somewhere you can retrieve it; you’ll use it to find the first record in a block explorer, a website that displays network activity.

Check the transfer in order

Follow the transfer from its source record to its destination result; this sequence shows where it stands and what to do next.

1. Find the source transaction. Open the sending network’s block explorer and search for the hash. Confirm the sender, token, amount, and destination details match what you intended. A wallet activity entry is useful, but the explorer record is the better place to verify the transaction itself.
2. Read the source status. If it is pending, the network has not included it in a block yet; wait for the status to change. If it failed or reverted, the transfer did not start successfully. Check the explorer’s error details before considering another attempt, so you don’t accidentally send twice.
3. Check for destination execution. Once the source transaction succeeds, look in the bridge’s transaction tracker if it provides one, or check the destination network’s explorer for the related transaction. Some bridges publish a separate destination hash or status. A successful source transaction with no destination result yet means the handoff may still be processing; it does not, by itself, mean the transfer failed.
4. Verify the destination balance and token. Switch your wallet to the receiving network and confirm the amount arrived at the intended address. If the balance looks unchanged, check the destination explorer for the token transfer and confirm the token contract matches the asset you expected. Wallets may not display every token automatically. Keep some of the destination network’s native token available if you’ll need to pay gas, the fee for later transactions.
5. Decide based on the last confirmed record. If the source is pending, wait; if it failed, investigate that transaction; if it succeeded but the destination is still pending, don’t submit another transfer while the first route may still complete. If the destination transaction succeeded but the wallet balance seems wrong, verify the address, network, and token contract before taking further action.

If you need the destination balance in a different asset, a cross-chain swap can combine moving and exchanging tokens in one flow. mantlebridge.us lets you arrange that kind of cross-chain transfer and swap; you still need to check the final token and network against what your destination app requires.

Decision rule: act only on the latest confirmed record—source failure calls for investigation, while a successful source with no destination result calls for checking the handoff before retrying.