When an Ethereum Deposit to Manta Pacific Is Stuck

An Ethereum-to-Manta Pacific transfer is stuck at the stage where its cross-chain message stopped progressing, not necessarily where your wallet stopped showing activity. A deposit starts with an Ethereum transaction; its receipt confirms what happened on Ethereum, while Manta Pacific’s history and explorer show whether the corresponding L2 action was executed. Those are separate checks. A confirmed L1 transaction alone does not prove that the asset is spendable on Manta.

Start with the transaction hash from your wallet or the bridge’s history, and verify that its source network is Ethereum Mainnet and its destination is Manta Pacific. The Manta bridge guide to supported assets and pending transfers covers the asset and status details that can complicate this check. Keep the hash; it lets you compare the source transaction with any destination record without relying on a wallet’s pending label.

How do I tell whether the Ethereum deposit was submitted?

Check the Ethereum transaction receipt: a transaction still pending in the mempool has not been mined, while a receipt with a reverted status means its execution failed. A successful receipt means the L1 transaction executed, but it does not by itself confirm an L2 credit. Check the block explorer using the transaction hash, rather than treating a wallet notification or a bridge spinner as the final record.

If the transfer used an ERC-20 token, check whether the wallet submitted an approval before the deposit. An approval authorizes a contract to transfer tokens; it is a separate Ethereum transaction and does not move the tokens across chains. If the approval is pending or reverted, the deposit may never have been submitted. If the approval succeeded, find the later transaction that actually initiated the bridge deposit.

For a submitted deposit, inspect the receipt’s logs and transaction details. The relevant evidence is a successful bridge-related call and the event or message that records the deposit for L2 processing. If the receipt reverted, the transfer did not complete on Ethereum, even if the interface briefly showed a submission. If there is no mined transaction hash at all, the wallet may still be waiting for a signature or for the transaction to enter the mempool.

Why can a confirmed deposit be missing on Manta Pacific?

A successful Ethereum deposit still needs its cross-chain message to be included and executed on Manta Pacific. The bridge’s history may show this as a later stage, and the L2 explorer may show the resulting transaction separately from the Ethereum transaction. Search using the destination address and the L1 deposit hash or message details shown in the bridge interface. Do not expect the L1 hash to be the L2 transaction hash.

Then check the asset itself. A token symbol is not a unique identifier across chains: compare the Ethereum token contract address with the corresponding Manta Pacific token address and confirm that the asset is supported by the route you used. A balance may be present under a different token contract than a wallet’s default token list recognizes. Add or inspect the verified Manta Pacific token contract before concluding that the funds were not credited.

Network selection can also make a valid balance look absent. Confirm that the wallet is viewing Manta Pacific and the same destination address used for the deposit. If the address matches but the token does not appear, inspect that address on the Manta Pacific explorer before making another transfer. The explorer’s on-chain record separates a display problem from a missing L2 execution.

What should I do when the bridge history stays pending?

Use the stage shown in the bridge history to decide what to check next. Match each stage to an on-chain record before taking action:

• Wallet submission: find the Ethereum hash and check whether the transaction was mined.
• Ethereum deposit: inspect the receipt status and confirm that the intended token and amount appear in the bridge transaction.
• Message processing: check bridge history and Manta Pacific for the corresponding L2 transaction.
• Destination balance: verify the receiving address, network and token contract on the Manta Pacific explorer.

If the Ethereum transaction is still pending, the source-chain transaction is the stage to resolve. If it reverted, inspect the revert reason before submitting again. If it succeeded and the bridge history has no corresponding L2 transaction, retain both the L1 hash and the bridge status; those details identify a message-processing delay more clearly than a screenshot of the wallet balance.

Do not submit a duplicate deposit simply because the first one is absent from the token list or the interface has not refreshed. First establish whether the original source transaction succeeded and whether its message was executed. If the bridge offers a specific recovery or retry action for that recorded deposit, use the documented action for that exact stage. Verify the bridge’s domain independently before connecting a wallet, and never share a seed phrase or private key to recover a transfer.

The useful distinction is between a pending Ethereum transaction, a failed L1 deposit, and a successful deposit whose L2 message or token display still needs checking. Follow the transaction hash across both chains, confirm the token contract, and act only on the stage the records show.