Transfer Pending? Check Both Explorers in Order

If a transfer is pending, compare its transaction record on the source and destination explorers: each shows a different stage of the same cross-chain operation. A successful source transaction means the source chain accepted it; it does not, by itself, prove that the destination assets have arrived. To diagnose the delay, follow the message from its source transaction to its destination execution.

What does “pending” mean on each explorer?

On the source explorer, check whether the transaction is pending, failed or confirmed according to that chain’s terminology. A confirmed transaction may still be waiting for the bridge’s required finality, message processing or destination execution. If your route uses Manta, see this guide to Manta Bridge deposit and withdrawal planning for route-specific preparation; explorer checks cannot show every step before you send.

Start with the source transaction hash and record the chain, status and any event or message identifier shown. Then check the bridge’s own transfer record, if available, for a destination transaction hash or a state such as queued or relaying. Status labels vary by bridge, so match identifiers and events rather than assuming that two screens use “pending” in the same way.

• Source transaction pending: the source chain has not yet confirmed it.
• Source confirmed, no destination hash: the bridge may still be waiting for finality or processing the message.
• Destination hash present: open it on the destination chain’s explorer and inspect its execution result.
• Destination transaction failed: the message arrived, but execution did not complete as intended.

How do you match a transfer across explorers?

Use the transaction hash on the source chain to locate the initiating transaction, then use the bridge record or message identifier to find its destination leg. A cross-chain transfer often involves separate transactions on separate chains, so searching the source hash on the destination explorer may return nothing. Check the destination chain selected in the bridge interface and verify that the receiving address matches your intended wallet.

Explorer timestamps can help establish sequence, but they do not prove that a bridge message has completed. Look for the destination transaction’s status and, where the explorer exposes it, the relevant token transfer or contract event. For tokens represented by a bridge-specific asset on the destination chain, confirm the token contract as well as the displayed symbol.

When should you retry or contact support?

Retry only after confirming that the original source transaction failed or that the bridge’s own instructions say the transfer can be safely resubmitted. If the source transaction succeeded, submitting again may create a second transfer rather than speed up the first. Keep the source hash, bridge message identifier, destination chain and any destination hash together when checking the bridge’s official status or contacting support.

Watch next for the destination transaction hash: once it appears, its execution result is the clearest signal of whether the transfer completed or needs follow-up.