Why Mantle Bridge Transfers Show as Separate Wallet Transactions

A Mantle bridge transfer usually appears as separate transactions because the source and destination networks record different steps. For a deposit, your wallet sends tokens on the source chain, the bridge processes that deposit, and the tokens become available on Mantle. The wallet’s history is a record of transactions on each network, not one combined receipt for the whole journey.

Why does a deposit appear in more than one place?

A deposit can leave one record on the sending network and another on Mantle. First, the wallet submits a transaction on the source chain, often Ethereum, that transfers tokens to the bridge. That transaction has its own hash and status. After the bridge processes it, a corresponding credit is recorded on Mantle, where the wallet can show the received tokens or a related transaction.

These records answer different questions: the source-chain transaction shows that you sent funds to the bridge; the Mantle-side record shows that the funds arrived. A wallet may show the first step as a contract interaction, while token balances or transfer details reveal the second. The mantle bridge guide explains the deposit and withdrawal process in more detail. If the destination entry is not visible in the wallet’s default activity list, check that Mantle is selected and inspect the address on a Mantle block explorer.

What does a withdrawal look like in wallet history?

A withdrawal starts with a transaction on Mantle and may require a later transaction on Ethereum before the funds are available there. First, you submit the withdrawal from Mantle through the bridge. That transaction can show as successful on Mantle even though the process is not finished. The bridge then has to process the withdrawal according to its rules; completing the process can involve a waiting period and a separate finalization step on the destination chain.

That means “successful” describes the transaction that the wallet sent, not necessarily the entire cross-chain transfer. A useful way to read the history is as a sequence of receipts: the Mantle transaction records the request, and a later Ethereum transaction records completion when required. The withdrawal may therefore have a different status on each network at the same time.

How can you match the wallet entries to the transfer?

Start with the network shown beside each history item. Then open the transaction details and compare the sending address, receiving address, token, and amount. A bridge transaction can include a contract call rather than a simple transfer directly to another personal wallet, so the wallet’s short description may not name every step.

• Deposit: find the outgoing transaction on the source network, then look for the corresponding token credit on Mantle.
• Withdrawal: find the withdrawal request on Mantle, then check for any required completion transaction on the destination network.
• Pending or missing entry: check the transaction status on the network where it was submitted, and confirm the wallet is displaying the intended account and network.
• Different amounts: compare the token and amounts in transaction details; fees or the particular transfer route can affect what arrives.

A block explorer can help when a wallet groups, abbreviates, or omits bridge-related activity. Search using the transaction hash on the same network where it was submitted; a hash from one chain will not by itself show the full journey on another.

What should you take away from separate entries?

Separate wallet entries are a normal consequence of a bridge coordinating activity across networks. Each network records its own transaction, and the wallet presents those records as activity rather than as one cross-chain event. For most readers, the clearest check is to follow the transaction hash on the sending network, then verify the resulting credit or completion step on the receiving network. What changed is the asset’s location and the set of network records attached to it; what to watch next is the status of any step that remains pending.