Check the transaction on the chain you sent from, then look for evidence that the swap reached its destination. A delay does not always mean the funds are lost: each chain and bridge route can take a different amount of time.
For example, a what a Manta bridge fixed rate covers is separate from how quickly a transaction confirms. The rate concerns the quoted exchange; network activity and the route affect when the destination transfer completes.
What does “pending” mean?
A cross-chain swap starts with a transaction on the source chain, the network where you send the asset. Once that transaction is included in a block, the bridge or swap route must process it before the destination chain can receive funds.
A block explorer is a public website that shows transactions on a particular chain. It can tell you whether your source transaction was included, how many confirmations it has, and sometimes whether a separate destination transaction was made.
Some routes use a relayer: software that watches one chain and submits a transaction on another. Others use different methods. A source transaction can succeed while the destination step is still waiting, so check both sides before deciding what happened.
How can you check the route?
Use the transaction record and the route’s status information to trace the transfer. These steps work whether you are moving USDC between networks or swapping one asset for another.
- Find the source transaction hash. It is a unique code for the transaction, usually shown in the wallet or transaction record. Copy it exactly.
- Open the block explorer for the source network and search for that hash. Confirm that the transaction succeeded and that the amount and destination details match your transfer.
- Check the confirmation count. A confirmation means the transaction has been included in a block; some routes wait for more confirmations before processing it. The required number depends on the chain and route.
- Check the route’s status for a destination transaction or completion record. If one is shown, open it in the explorer for the destination network and confirm that it succeeded.
- Verify the receiving address and asset on the destination network. A token with the same ticker can have different versions, so check the token details as well as the displayed name.
For instance, if you send USDC from Ethereum to Solana, an Ethereum success alone does not prove that USDC has arrived on Solana. Look for the destination transaction and check the receiving address in a Solana explorer.
When should you take action?
If the source transaction failed, the swap did not complete from that transaction. Check your wallet’s balance and transaction record before trying again. If it succeeded but the destination step is pending, avoid sending a second swap to “unstick” the first one.
If no destination transaction appears, compare the route status with the source confirmations. Congestion, the route’s confirmation requirements, and its processing method can all affect timing. There is no single delay that proves a transfer is stuck.
Manta bridge is one service for moving and swapping assets across chains. Whatever route you use, keep the source hash until the destination transfer is confirmed. A useful habit is to verify the network and address before sending; those details are harder to fix after confirmation.