A confirmed transfer can still be pending until the destination chain processes its message; the wait depends on the direction and route. Unlike an exchange, a bridge moves value between two separate blockchains, so one transaction does not update both balances at once.
What does “confirmed” mean on each chain?
A confirmation means the source chain recorded your transaction. For an Ethereum-to-Mantle deposit, the transaction locks or sends the asset through the bridge contract on Ethereum and creates a message for Mantle. A relayer, a service that carries messages between chains, then helps process that message on Mantle.
That creates two useful checkpoints: the source transaction and the destination credit. If your wallet says the Ethereum transaction succeeded but your Mantle balance has not changed, the transfer may still be waiting for the message to be processed. A successful token approval is an earlier, separate transaction; by itself, it does not make a deposit.
For a Mantle-to-Ethereum withdrawal, the order is different. Mantle records the withdrawal, then the network batches its transactions and submits a proof to Ethereum. A ZK validity proof is a compact mathematical check that the batch followed the rules; after Ethereum verifies it, the bridge can release the asset, sometimes after a separate claim transaction.
Why can the wait differ by direction?
Deposits and withdrawals use different chains to settle the important parts. Ethereum congestion can slow a deposit’s source transaction, while Mantle’s message processing affects when the destination balance appears. For withdrawals, batching and proof generation add stages before Ethereum can release the funds.
Mantle now uses validity proofs, and its documentation says a verified batch reaches finality without a challenge period. That means an old “wait seven days” estimate may not describe the current proof system. Actual wait time still varies with transaction inclusion, batch timing, and network activity.
The route also matters: a liquidity route may deliver funds through available liquidity, while a canonical route follows the network’s settlement process. When you use the Mantle Bridge service, treat the source transaction hash as evidence of the first step, then check whether the destination transaction or balance change has occurred.
What should you check if the balance is missing?
Start with the source transaction hash in that chain’s block explorer, a public record of blockchain activity. Confirm it says successful, and check the destination address shown in its details. Then view that same wallet address on Mantle or Ethereum, depending on where the funds should arrive.
If the address is right but the token is absent, check the token’s contract address on the destination chain. A token can have the same name or ticker as another token while using a different contract, and some wallets hide tokens until you add that contract. For a withdrawal, also check whether the bridge has reached the claim stage.
For example, after sending ETH from Ethereum to Mantle, an Ethereum success notice does not prove the Mantle credit is complete. Check for the destination event before retrying; a second deposit could send more ETH. Mantle Bridge is one way to make this transfer, but the same two-chain checks apply when using a wallet directly.
Before you start, keep the source hash and confirm you have the destination chain’s native token for any later transaction fees—ETH on Ethereum or MNT on Mantle.