Check Both Sides of a Mantle Bridge Transfer

2 checks confirm a Mantle Bridge transfer in an app: the source transaction and the destination balance. They show whether your request was submitted and whether the asset reached the wallet on the other network. One green status is not proof that the full transfer is complete.

What does a bridge app status tell you?

A bridge app tracks a cross-network message that begins with a transaction on one chain and is processed on another. “Submitted” or “pending” usually means the source transaction was sent, but the destination step may still be underway. A “complete” label is useful, but check what the app means by it.

For a deposit from Ethereum to Mantle, the app can show the Ethereum transaction before the Mantle-side balance appears. For a withdrawal, starting the request on Mantle may not release funds on Ethereum; the process can include a later settlement and claim step. The mantle bridge guide explains when this route fits and what to expect from each direction.

How do you verify a transfer in the app?

Open the transfer’s details and note the transaction hash, the long identifier for its on-chain record. Check that it belongs to the right wallet and source network, then use the relevant network explorer to inspect its status. A confirmed source transaction means it was recorded on that chain; it does not, on its own, confirm receipt on the destination.

Then switch the wallet or app view to Mantle for a deposit, or Ethereum for a withdrawal, and check the receiving address and token balance. Confirm that the asset is on the expected network: the same wallet address can exist on both chains, while balances and token contracts are separate. If the explorer shows funds arrived but the app balance does not, refresh the view and check that the app is displaying the right network and token.

Why can a transfer look complete on one side?

The two chains record separate parts of the transfer. An app may update after it sees the source transaction, while the destination message is still being processed; a withdrawal may also wait for a separate claim. The exact status labels vary, so use the transaction details and destination balance to establish what has happened.

Keep the source hash until you have checked the receiving side. If the transfer remains pending, compare its current app status with the corresponding explorer record before retrying: submitting a second transfer can move another amount without resolving the first one.

What should you check before treating it as finished?

Use these checks in order. They separate a submitted request from funds you can actually use:

• Match the wallet address and source and destination networks to your intended route.
• Check the source transaction hash and confirm its status in the source explorer.
• Look for the expected token and amount at the receiving address on the destination network.
• For a withdrawal, check whether the app requires a separate claim and whether it has been completed.

Bridge apps make progress easier to follow, but the underlying records live on each chain. Treat the transfer as complete when the destination side shows the expected funds and any required claim is done.