Trace a Mantle Deposit That Has Not Arrived

Trace a missing Mantle deposit by following its Ethereum transaction to the corresponding credit on Mantle. A wallet’s token list is only the last check: the source transaction, bridge message and destination balance each reveal a different failure point. Save the Ethereum transaction hash and the receiving address before checking anything else. The Mantle Bridge explainer covers the wider deposit and withdrawal path; here, the useful distinction is between a transaction that never deposited and one whose destination credit is not yet visible.

Did the Ethereum transaction actually deposit the asset?

The Ethereum transaction receipt tells you whether the deposit call succeeded. Search the hash on an Ethereum block explorer and inspect its status, destination contract and emitted events. A successful receipt means the EVM call completed; it does not, by itself, prove that the asset is already credited to the destination wallet on Mantle.

First rule out an approval mistaken for a deposit. An ERC-20 transfer commonly requires an allowance transaction before the bridge can spend the token. That approval updates the token’s allowance for a spender; it does not move the deposit amount into the bridge. If the hash points to an approval, return to the bridge interface and check whether a separate deposit transaction was submitted. ETH deposits do not use an ERC-20 allowance, but they still require their own transaction.

If the transaction reverted, the deposit did not complete. The receipt may still show a gas fee because the failed call consumed gas, but a reverted transaction’s state changes—including token transfers—are rolled back. Check the revert reason if the explorer provides one, then address the cause before submitting again. If the transaction is pending or absent from the explorer, check the wallet’s activity and nonce: a queued transaction or a dropped submission is not a completed bridge deposit.

What should I check while the deposit is processing?

A successful Ethereum deposit starts the cross-chain path; Mantle must then process the message and credit the destination. Check the bridge’s transaction history, if available, and search the receiving address on Mantlescan. Use the destination network’s explorer for the destination balance and transaction, and the Ethereum explorer for the source receipt. These are separate records because the bridge action begins on one chain and its effect appears on another.

Compare the addresses and asset details from the signed transaction with the transfer you intended. Confirm the recipient encoded in the deposit call, the source token contract, the selected route and the corresponding token contract on Mantle. A correct source transaction sent to a different recipient will not appear in your wallet. Nor does a matching ticker prove that two token contracts represent the same asset.

Use these checks to classify what you see:

• Approval only: no deposit transaction appears on Ethereum. Submit the deposit separately if you still intend to bridge.
• Reverted or pending: the source transaction has not completed successfully. Read its receipt before retrying.
• Successful source, no destination credit: inspect bridge history and Mantlescan for a corresponding destination transaction or message status.
• Destination transaction succeeded, wallet balance absent: check the receiving address, network selection and verified token contract displayed for the asset.

A deposit is not the same operation as a withdrawal. For a deposit, the source-side transaction is on Ethereum and the receiving credit is on Mantle. Do not look for an Ethereum claim step: that pattern belongs to some withdrawal flows, where a later action releases funds on Ethereum. Applying the withdrawal sequence to a deposit can lead you to search for a transaction that the deposit path does not require.

Why can a credited deposit still look missing?

A completed Mantle transaction may not change the balance view currently open in your wallet. Switch the wallet to Mantle and confirm that its selected account matches the recipient in the bridge transaction. If the Mantle explorer shows a successful transaction to that address, inspect the token transfer in its logs. A native currency transfer appears differently from an ERC-20 token transfer, and an ERC-20 balance may require the wallet to display the correct verified token contract.

Check the asset mapping before importing a token. Use the destination contract identified by the bridge or a trusted Mantle token listing; do not copy the Ethereum contract address simply because the token has the same name or symbol. A wallet display issue does not reverse an on-chain credit, while a transfer to a different address cannot be fixed by importing a token.

When is a pending deposit a support issue?

Escalate when the Ethereum receipt shows a successful deposit, the expected recipient and token are correct, and the bridge history or destination explorer still shows no corresponding processing after a reasonable wait. Provide the source transaction hash, source and destination addresses, token contract, amount and approximate submission time. Those details let support correlate the on-chain event with the bridge record without exposing wallet credentials.

Never share a seed phrase or private key to “release” a deposit. A confirmed bridge transaction cannot be cancelled by closing the site or revoking an allowance. The useful dividing line is evidence: a receipt proves what happened on Ethereum, and a destination transaction or balance proves what happened on Mantle. Follow those records in order, and you can distinguish a wait in processing from an approval-only submission, a failed call, a display problem or a recipient mismatch.