Verify a Mantle Bridge Deposit on the Destination Chain

A Mantle deposit has arrived when the corresponding transaction succeeds on Mantle and credits the intended recipient with the expected asset. An Ethereum transaction marked successful proves only that the source-chain call completed; it does not, by itself, prove the destination credit.

Which transaction proves the deposit arrived?

The Mantle destination transaction and the recipient’s balance provide the receipt check. The canonical bridge starts a cross-chain deposit from Ethereum, then the bridge message is processed on Mantle. Those are separate chain records: the source transaction hash and the destination transaction hash can differ.

Start with the hash for the deposit transaction, not an earlier token approval. An ERC-20 deposit may require an approval transaction before the bridge can transfer the token. Approval grants permission; it does not move the deposit. The Mantle Bridge account covers the route mechanics and the withdrawal-side split; this check focuses on whether a deposit reached its destination.

Open the Ethereum transaction in its explorer and confirm that it succeeded. Then use Mantle’s explorer to find the related L1-to-L2 transaction. The explorer lists paired source and destination hashes under its cross-chain transaction views. A source success with no corresponding destination transaction is evidence that the deposit was initiated, not that the recipient has been credited.

How do you match the Mantle transaction to your deposit?

Match the destination record against the recipient, token, and amount. On Mantle’s explorer, open the L2 transaction and inspect its status and token transfer details. Confirm the destination address is the address you intended to receive funds, especially if the bridge form allowed a recipient different from the connected wallet.

Check the token contract address as well as its ticker. Different assets can share a symbol, and the same asset may have different token representations across chains. A displayed name alone does not establish that the received token is the one you meant to bridge.

• Compare the source transaction hash with the L1 hash shown in Mantle’s cross-chain record.
• Confirm that the paired Mantle transaction succeeded.
• Check that its recipient matches the intended Mantle address.
• Verify the token contract and credited amount, accounting for any amount shown as transferred rather than the amount entered in the form.

For a second check, search the recipient address on Mantle and inspect its token balance or transfer history. A balance is useful corroboration, but it is not enough on its own: the address may already have held the same token before the deposit. The transaction record ties the new credit to the specific bridge operation.

What if the Ethereum transaction succeeded but Mantle shows no funds?

A successful Ethereum receipt means the source transaction was included and executed; the Mantle-side message may still be processing. Check the bridge history and the explorer’s L1-to-L2 view using the source hash before repeating the deposit. Submitting another deposit creates another source transaction and may send funds twice if the first message is merely delayed.

If a paired destination transaction appears but failed, inspect its error or status details. A failed destination execution does not establish that the intended token balance was credited. Keep both hashes and compare the logged recipient and token data with the original bridge parameters. If the bridge interface reports completion while the explorer shows no successful Mantle transaction, treat the discrepancy as unresolved and use the official bridge’s support route with the transaction hashes.

If the destination transaction succeeded but the asset is absent from the wallet display, check the address on Mantle’s explorer and verify the token contract. Wallet interfaces can omit unfamiliar tokens from the visible list. Adding a token display entry changes what the wallet shows; it does not itself create or recover a balance.

When is the deposit confirmed?

For a practical receipt check, confirm the successful Mantle transaction and the credited balance at the intended address. The destination record is stronger evidence than a bridge screen that says “submitted,” a wallet notification, or the Ethereum receipt alone. The source hash documents the initiation; the destination hash documents execution on Mantle.

Keep the source and destination hashes together if you need to reconcile the transfer later. Also retain the token contract address and recipient address, since a ticker or wallet label can be ambiguous. If no destination transaction exists yet, use the bridge history and explorer record to track the same deposit rather than inferring arrival from elapsed time.

Confirmed: the source transaction succeeded, the paired Mantle transaction succeeded, and its transfer record credits the intended address with the intended token. Still unverified by those checks: whether the balance remains there after later transactions, or whether the asset can be redeemed through a separate route.