A Pending Cross-Chain Transfer Needs Two Checks

To check a pending cross-chain transfer, confirm its transaction on the source chain, then follow the bridge’s status record to destination delivery or a refund. A wallet’s “pending” label compresses several steps into one, while a normal single-chain transfer usually has one transaction to inspect. The useful question is not simply whether the transfer is complete, but which part of the route has finished.

Start with the source transaction hash in the bridge interface or wallet history. Open it in an explorer for the chain you sent from and check whether it was included in a block and succeeded. A transaction that is still waiting in the wallet has not yet begun the bridge’s cross-chain work; one that reverted did not make a successful deposit. If the source transaction succeeded, keep its hash and use the bridge’s own tracker to look for the next stage. For the distinction between same-asset routes and cross-asset transfers, the fuller mayan bridge explainer adds useful context; the status checks below apply either way.

What does pending mean on a cross-chain transfer?

“Pending” means the route has not reached its final state in the service showing that label; it does not identify the step that is waiting. A bridge may need to observe the source transaction, wait for the source chain’s required confirmations, relay a message or proof, and execute a transaction on the destination chain. Some routes also require the recipient to claim funds. These stages can be shown with different names, and not every bridge uses the same sequence.

That difference matters because a successful source transaction is evidence that the origin-side action happened, not proof that the destination balance has been credited. Likewise, a tracker that has not refreshed may lag behind the chain. Treat the explorer as the record of what happened on each individual chain and the bridge tracker as a guide to how the service connects those events.

How do you check each stage of a pending transfer?

Use the same transaction identifier throughout the check, and compare the route details shown in the wallet with the bridge tracker: source chain, destination chain, asset, amount and recipient address. Then verify the source transaction in the correct chain explorer. If it succeeded, check the bridge’s status page using the source hash or transfer ID, and look for a destination transaction hash, a claim step or a refund status.

• Source not confirmed: The transaction may still be queued or awaiting inclusion. Check its explorer status before treating the bridge as the cause.
• Source succeeded, destination absent: The bridge may be waiting for confirmations, relaying a message or processing a route. Check the bridge tracker again after a reasonable interval.
• Destination transaction shown: Open that hash in the destination chain’s explorer. Confirm it succeeded and check the recipient address and token balance there.
• Claim or refund shown: Read the route’s instructions and verify the relevant transaction on-chain. A claim is a separate destination action; a refund should be confirmed on the source chain.

When checking a destination balance, make sure the wallet is displaying the destination network and the correct token. A transfer can arrive as a token that looks similar to the one sent but has a different contract, or as the output of a cross-asset route. The tracker’s destination amount may also differ from the source amount if the route exchanged assets or charged fees. Compare the stated route and actual destination transaction rather than expecting every number or token label to match.

What should you do if the transfer stays pending?

If the source transaction succeeded but no destination transaction appears, use the bridge’s official tracker and support route to check whether the transfer needs time, a claim or recovery. The right next step depends on the route: another transfer will create a separate transaction and will not resolve the first one. Before taking action, confirm the destination network, recipient address and any instructions attached to this specific transfer. Never share a recovery phrase or sign an unrelated transaction to “release” funds.

Keep the source hash, transfer ID, route, timestamp and any destination hash together when seeking help. Those details let support trace the transfer without asking you to repeat it. If the tracker reports success but the wallet shows no funds, verify the destination transaction and token in an explorer first; the display may need the right network or token entry to show the balance.

The practical dividing line is the source transaction’s on-chain result. If it has not succeeded, investigate the wallet transaction. If it succeeded, follow the bridge’s status and destination evidence rather than relying on a generic pending label. Watch for a destination hash, a claim requirement, a refund record or a tracker status that remains unchanged beyond the route’s stated processing window; those signals determine whether to wait, complete a step or contact the bridge.