A confirmed wallet transaction does not always mean a withdrawal has reached Ethereum. With a Manta Bridge withdrawal from Manta Pacific, the first confirmation generally records the exit request on the source network; later actions may still be needed before the asset is available on Ethereum. The useful response is to identify the stage, preserve the transaction hash, and avoid sending the same withdrawal again.
A confirmed transaction may only be the withdrawal’s first stage
Cross-chain withdrawals are not the same as sending ETH between two addresses on one network. An exit from an L2 back to Ethereum can involve an initiation transaction, proof-related processing, a waiting period, and a final Ethereum-side transaction. A wallet may correctly show the first transaction as successful while the broader withdrawal remains unfinished.
That distinction prevents a common mistake: treating “confirmed” and “received” as interchangeable. They answer different questions. The first means the source-network transaction was included in a block. The second means the withdrawal has completed its required path and the destination-side balance can be used.
Before troubleshooting, record three items: the source transaction hash, the asset and amount, and the wallet address used for the withdrawal. These let you compare the bridge history with an explorer without relying on a browser tab or a wallet notification.
Check the route before deciding that funds are missing
Start by confirming that the transaction was initiated on Manta Pacific and that the intended destination was Ethereum. A token balance can appear absent simply because the wallet is still displaying the source network, the destination token is not visible in the wallet interface, or the transaction was made through a different route than expected.
- Open the transaction hash on the explorer for the network where you initiated the withdrawal.
- Confirm the sending wallet, asset, and transaction status match your records.
- Check the bridge’s transaction history for the current withdrawal state and any available next action.
- Switch the wallet to Ethereum only after the route indicates that the Ethereum-side step is ready.
If your wallet shows the initiation transaction as confirmed, the decision is not to resend it; first determine which withdrawal stage is still incomplete. Manta Bridge is the relevant place to check the route and status sequence for that specific withdrawal. Treat the displayed stage as a task list, then act only on the next transaction the route calls for.
Use the status to choose the next action
A pending withdrawal usually falls into one of four practical categories. The exact labels can vary by interface, but the decision rule stays the same: do not repeat an earlier transaction when the system is waiting for a later one.
| What you see | What it usually means | What to do |
|---|---|---|
| Source transaction still pending | The withdrawal request has not finalized on Manta Pacific. | Wait for confirmation and do not create a duplicate request. |
| Withdrawal recorded but no next button | The route may be processing data or waiting for a required period. | Keep the hash and recheck history later rather than changing wallets or assets. |
| A proof or completion action is available | The withdrawal has advanced, but needs a transaction on Ethereum. | Switch to Ethereum, verify the prompt, and ensure the wallet has ETH for gas. |
| Final action confirmed but token is not visible | The asset may be present but not shown in the wallet interface. | Verify the destination address and token balance through an explorer before importing anything. |
Do not turn a delay into a duplicate withdrawal
The operational risk is not only waiting. Repeating a transaction because the interface looks inactive can create a second withdrawal request, additional gas costs, or confusion over which transaction is being tracked. Use the original hash as the reference point until you can show that it failed or was replaced.
A worked example: a user withdraws an ERC-20 from Manta Pacific, sees the source transaction confirm, then checks Ethereum ten minutes later and sees no balance. That does not establish a failure. The correct sequence is to inspect the bridge history, determine whether an Ethereum-side action is available, and compare the wallet address on both explorers. Only after those checks should the user decide whether any new transaction is necessary.
Also keep enough ETH for the transaction that may be required on Ethereum. Receiving an instruction to prove or complete a withdrawal is not useful if the wallet cannot pay the network fee for that step. Avoid accepting unfamiliar wallet signatures, especially permits or approvals unrelated to the withdrawal you are tracking.
Escalate with evidence, not screenshots alone
If the status has not changed after the route’s expected processing path and no next action is available, collect the source hash, destination address, asset, amount, and a description of the displayed state. Never share a seed phrase, private key, or recovery words to obtain support.
Your next action is simple: locate the original withdrawal in bridge history, identify its current state, and complete only the next verified step attached to that transaction.