Ethereum-to-Mantle deposits can wait at two different stages
An Ethereum-to-Mantle deposit can stay pending during Ethereum confirmation or Mantle message relay; the transaction hash shows which step is waiting and what to do next.
By Web3 Hub Newsroom3 min read
An Ethereum-to-Mantle deposit can stay pending because Ethereum has not confirmed the source transaction or Mantle has not relayed its message to the destination. Mantle’s bridge records a source-side deposit on Ethereum, then processes the cross-chain message before the funds appear in the Mantle wallet.
Those are separate steps, so “pending” alone does not show where the delay is. The Mantle Bridge guide explains the fee mechanics; the transaction hash is the first thing to check when a transfer stalls.
What does “pending” mean on an Ethereum-to-Mantle deposit?
If the Ethereum transaction is still pending in the wallet or explorer, it has not yet been included in a block. Network congestion or a low gas fee can delay inclusion; the bridge cannot process a deposit that Ethereum has not recorded.
If the source transaction is confirmed, the deposit has cleared that first step, but the bridge message may still be waiting for Mantle to relay it. Mantle’s SDK distinguishes an unconfirmed L1-to-L2 message from one that has been relayed, showing that a confirmed Ethereum receipt and a completed Mantle credit are different states.
How can I tell which step is holding up the transfer?
Look up the transaction hash on an Ethereum block explorer and check its status. A pending transaction is still waiting on Ethereum; a successful receipt means the source transaction landed, so check the bridge’s History view and the destination wallet next.
Mantle’s official bridge page provides a History tab, and its interface lets users select Ethereum as the source and Mantle as the destination. Compare the transaction’s destination address and asset with the wallet and token you expect; a token balance may not appear under the symbol you first search for if the wallet has not added that token contract.
For an ERC-20 deposit, check whether the wallet submitted two transactions: an approval and the actual deposit. An approval permits the bridge contract to use the token; it does not move the token by itself. A confirmed approval with no deposit transaction means the transfer has not started.
What should I do while the deposit is pending?
Use the stage shown by the records to decide what to do. Avoid submitting the deposit again while the original transfer may still complete, since a second confirmed deposit would be a separate transfer.
- If Ethereum shows “pending,” wait for inclusion or use the wallet’s supported fee-bump option.
- If Ethereum shows “failed” or “reverted,” check the receipt before trying again; the intended deposit did not complete, though the failed transaction may still have used gas.
- If Ethereum shows “success,” check bridge History and the Mantle wallet address for the destination credit.
- If the source succeeded but the bridge history remains stuck, keep the hash and contact Mantle support through its official site.
Do not share a seed phrase or approve an unsolicited recovery transaction. A support account does not need wallet secrets to look up a public transaction hash.
When is a pending deposit a cause for concern?
A short wait after Ethereum confirmation can reflect the time needed to process the cross-chain message; it is not proof that funds are lost. A source transaction that remains pending for longer than expected, a failed receipt, or a successful receipt with no corresponding bridge-history entry calls for a closer check.
Start with the hash, confirm the source-chain result, then use the official bridge History and destination wallet to trace the next step. If the message is still missing after those checks, send support the hash and wait for its response before making another deposit.