To track an Ethereum-to-Mantle transfer, follow its source transaction until the bridge message is relayed and the destination balance changes. The source transaction hash identifies the action on the network you sent from; it does not, by itself, prove the transfer finished. If you still need to start a transfer, the Mantle Bridge is one way to move supported assets between Ethereum and Mantle Network. Keep the wallet address and transaction hash handy so you can check both sides.
What Do You Need Before You Look It Up?
You need the transaction hash, the sending wallet address, and the direction of travel. A transaction hash is a long string of letters and numbers shown in your wallet’s activity; copying it is more reliable than searching by amount, which may appear differently after fees or token decimals.
First check which network the transaction used. For a deposit to Mantle, the starting transaction is on Ethereum; for a withdrawal to Ethereum, it is on Mantle. A wallet can show the same address on both networks, but the balances and transaction histories are separate. Think of each network as a separate branch of a bank: the same account name can exist at both, while a transfer between branches still needs its own record at each end.
Open the transaction in an explorer for the source network. A block explorer is a public record of transactions, balances, and contract activity. Mantle’s official developer tutorials describe checking a deposit transaction and then waiting for its message status to become relayed; Ethereum.org also explains that a bridge transfer involves activity across both networks.
How Can You Tell Whether the Transfer Is Still Moving?
A source transaction marked pending has not yet been confirmed by its network, so the bridge may not have started processing it. If it is marked failed, inspect the explorer’s error or status details: the transfer did not complete, though a separate token approval may still have succeeded.
When the source transaction is confirmed, check whether the corresponding cross-chain message has been relayed and executed on Mantle. A bridge carries instructions as well as assets: the source side records the deposit, then a relayer or bridge mechanism delivers the message that credits the destination address. This second part can take additional time, so a confirmed Ethereum transaction and an unchanged Mantle balance can briefly coexist.
For example, if you send ETH from Ethereum, first confirm that the Ethereum transaction succeeded. Then check the same receiving address on Mantle Network and look for the credited ETH or a completed destination event. The source hash is your starting point; where a bridge’s status information is available, use it to match the source action to the destination result.
Why Might the Balance Not Match What You Expected?
The most useful test is whether the destination transaction or message completed for the correct address and asset. Check the receiving address character by character, confirm that your wallet is displaying Mantle rather than Ethereum, and look at the token’s contract or symbol in the destination explorer. A token with a familiar name can have different contracts on different networks.
An ERC-20 token may also require an approval transaction before the actual deposit. Approval gives a contract permission to use a specified token amount; it does not move the tokens across networks. If your wallet shows an approval but no deposit transaction, search the activity again for a later transaction. MNT, ETH, and other assets can also have different representations on the destination network, so compare the asset and amount shown by the bridge message rather than relying only on a ticker.
One short safety check: use the official explorer for the network shown in your transaction, and never share your wallet’s recovery phrase or private key to “release” a transfer. A public transaction hash is safe to look up, but it does not authorize anyone to move your funds.
What Should You Do If It Still Has Not Arrived?
If the source transaction is confirmed but the destination side has not updated, compare the wallet address, asset, and bridge-message status before trying again. A second deposit could send more funds without resolving the first one. Timing depends on source-network confirmation, bridge processing, and network traffic; a delay alone does not establish that funds are lost.
For a withdrawal from Mantle to Ethereum, expect a different path: the Mantle transaction starts the withdrawal, and the bridge’s finalization process may require additional proof or a later claim on Ethereum. Do not treat the faster deposit path as a timing promise for withdrawals. The exact next action depends on the withdrawal’s recorded status and the bridge route used.
For your next step, copy the source hash from your wallet, open it in the matching network explorer, and verify that the destination message or balance change completed at the intended address. If you have not sent the assets yet, Mantle Bridge can handle a supported transfer between Ethereum and Mantle; once it is underway, use the two-network record to follow it through.