Cross-chain tracking means matching a transfer on one blockchain to its result on another. The key is that a confirmed send on the first chain does not prove the funds have arrived on the second.
If you are used to an exchange, this can feel unfamiliar: your wallet history may show only the transaction you signed. For an Ethereum-to-Mantle transfer, Mantle Bridge is the official bridge for moving ETH, MNT, and supported tokens between the networks.
What records should you check?
Start with these four details. They help you follow the transfer even if your wallet’s activity list looks incomplete.
- Source transaction hash: the ID for the transaction you sent.
- Destination transaction hash: the ID for the transaction that completes on the other network.
- Wallet address and network: the account receiving funds, checked on the correct chain.
- Token transfer record: the on-chain entry showing which token moved and how much.
A transaction hash is a unique ID for one transaction. Open it in an explorer for the network where you sent it: an Ethereum hash belongs in an Ethereum explorer, while a Mantle hash belongs in a Mantle explorer.
The destination transaction has its own hash. It may not appear in your wallet’s history because a bridge contract, rather than your wallet, performs that part. Search your receiving address on the destination network and check its token transfers as well as its ordinary transactions.
How do you tell where the transfer is?
Follow the records in order. First, check that the source transaction succeeded and that its token and amount match what you intended. Then check the bridge’s transfer record, if available, and look for the matching destination activity.
For example, say you send 0.1 ETH from Ethereum to your own Mantle address. The Ethereum transaction can succeed while the Mantle credit is still processing. Check the destination address on Mantle, confirm you are viewing the right network, and look for the ETH token balance or transfer entry there.
Withdrawals can involve more than one transaction or wait for additional network processing. A pending status does not necessarily mean the first transaction failed. If the source transaction succeeded but the destination record is missing, keep its hash and check the bridge’s transfer status before trying again.
One easy mistake is checking the right address on the wrong network. MetaMask can use the same address on both chains, but each network has its own transaction history and token records. In practice, I check the chain name, address, token, and amount before deciding that funds are missing.
For the actual transfer steps, see Mantle Bridge deposit and withdrawal steps. Once you know which records belong to each network, save both hashes for your next transfer and compare them with the destination balance.
Why does my wallet show only one transaction?
Your wallet usually records transactions you signed from that account. A bridge may create a separate transaction on the destination chain, so it can be missing from the wallet’s activity list. Search your receiving address in the destination network’s explorer and check token transfers there.
Can the same address have different histories?
Yes. A wallet address can be used on both Ethereum and Mantle, but each network keeps its own transaction history. Choose the correct network in your wallet or explorer, then check the same address there. A balance on one chain does not automatically mean the asset is on the other.
What if the source transaction succeeded but nothing arrived?
Keep the source hash and confirm its status, destination address, token, and amount. Then check the receiving address on the destination network and review the bridge’s transfer status. Cross-chain transfers can take time to finish. Avoid sending a second transfer until you understand the status of the first.
Where do I find the destination transaction hash?
Look in the bridge’s transfer record, if one is available, or search the receiving address on the destination chain’s explorer. Some transfers have a separate destination transaction; others may show the result as a token transfer or contract event. The source hash alone may not identify that destination activity.