A Cross-Chain Transfer Needs Two Checks

To check a cross-chain transfer, match its source transaction to the route’s status and then confirm the expected asset arrived on the destination chain. A wallet’s “submitted” message usually means the first transaction was sent, not that the transfer finished. That is different from a same-chain transfer, where one transaction record can usually show the full movement. Cross-chain routes add a second network and often a message or liquidity provider between them, so one green check may describe only one stage.

Start with the transaction hash in the wallet’s activity view. Open it in the explorer for the source chain and check whether it succeeded, failed or is still pending. A successful source transaction proves that the source network accepted the action; it does not by itself prove delivery. For a broader explanation of how omnichain apps coordinate assets across networks, see the fuller guide. Here, the practical distinction is between confirming the transaction you sent and confirming the result you expected.

What does each transfer status mean?

Transfer statuses describe separate steps, and their wording can vary by wallet or route. Treat each status as a clue about where to look next, not as a substitute for checking the chain record.

• Pending: The source transaction may not yet be included in a block. Check the source explorer before assuming the route has started.
• Confirmed or successful: The source chain recorded the transaction. Look for the route’s next step and the destination-chain result.
• Processing: A bridge, relayer or liquidity provider may still be handling the cross-chain message or payout.
• Completed: Check the destination explorer or wallet balance to confirm the expected asset and amount arrived.

A route can use a message to trigger an action on the destination chain, or it can pay out from liquidity already available there. Those designs have different steps, but the check is the same: find evidence on the destination network. A delay after source confirmation does not necessarily mean failure. If the route supplies a separate transfer or message identifier, use it in the route’s own status view; the source transaction hash may not identify every later step.

How do I confirm the asset arrived?

Check the destination chain named in the route, then inspect the destination transaction or token balance. Confirm that the token is the one you intended to receive, since a similar name or ticker can refer to a different asset. Also compare the amount with the route’s displayed output, allowing for any fee or conversion the route disclosed. A wallet may hide a token that has arrived until you add or enable its display, so a missing balance alone is not proof that delivery failed.

The alternatives have trade-offs. A direct wallet transfer is simpler when both wallets use the same chain, but it cannot move value between networks. A centralized exchange can accept a deposit on one network and let you withdraw on another, but that adds custody and requires matching the exchange’s supported deposit network. A bridge or cross-chain app keeps the transfer onchain, yet introduces extra stages to track. For most readers, the better choice is the route they can identify and verify end to end, rather than the route with the fewest visible taps.

When should I retry a transfer?

Retry only after checking whether the original source transaction failed or whether the route provides a recovery step. If the source transaction succeeded but delivery is still pending, sending again can create a second transfer rather than speed up the first. Keep the transaction hash and route identifier available when checking status. Never share a recovery phrase or private key with anyone claiming to resolve a delayed transfer.

Watch for three signals: the source transaction’s final status, a destination transaction or payout record, and the destination balance in the expected asset. Those checks separate a slow route from a failed source transaction and from an asset that arrived but is not displayed. Until the destination record appears, treat the transfer as in progress rather than complete.