Cross-Chain Transfer Status in 2026: How to Check Completion

A transfer is complete when the destination transaction succeeds. A “sent” or “pending” message usually means only that some part of the route has started, so check the source and destination separately before deciding what to do next.

A cross-chain transfer can involve several steps: your wallet submits a transaction on the source network, a bridge or service processes it, and a later transaction delivers the asset on the destination network. For example, a bungee bridge route may combine bridging and swapping, so the asset arriving can have a different token name from the one you sent. The source transaction hash alone cannot prove that the final step succeeded.

What does each transfer status tell you?

Status labels describe stages, and the exact wording varies by service. “Pending” often means the source transaction has not yet been confirmed or the route is still being processed; “completed” should correspond to a successful destination transaction, not merely a submitted source transaction.

Use the source transaction hash to open the transaction on the source network’s block explorer. Look for a successful result and a block or confirmation record. If it says failed, the route did not begin as intended; if it is still pending, wait for the network or wallet to update before attempting anything else.

Once the source transaction succeeds, find the route’s destination transaction hash or open its status details. Check that hash on the destination network’s explorer. A successful destination transaction is the strongest practical sign that the transfer arrived; match the receiving address and token to your intended destination.

How do you check that the right asset arrived?

Confirm the destination network, wallet address, token, and amount. A cross-chain swap can deliver a different token than the one sent, and fees or the exchange rate can make the received amount lower than the quoted amount. Compare the actual result with the route details shown before you approved it.

For example, imagine you sent a token from Polygon to Base and the route included a swap. Before, your wallet showed the source token on Polygon and the destination balance was empty. After, the destination transaction succeeds on Base, the receiving address matches your wallet, and the expected output token appears there. That combination is better evidence than a balance change on the source network alone.

If the destination token does not appear, check the wallet’s selected network and token list. The asset may have arrived but not be displayed automatically; use the token’s verified contract address from a reliable project or network source before adding it. Never trust a token just because its name or ticker matches.

How long should you wait before taking action?

There is no single safe wait time for every route. Timing depends on source-chain confirmation, the bridge’s processing and finality requirements, destination-chain congestion, and any swap or relayer step. A fast source confirmation does not guarantee instant delivery on the destination.

Check the route status first, then inspect both transaction hashes. Ethereum.org explains that block inclusion and finality are distinct concepts on Ethereum; Chainlink’s CCIP documentation likewise describes waiting for source-chain finality before validating and executing a cross-chain message. These are useful reminders that one chain can show success while the cross-chain work is still underway.

If the source transaction succeeded but there is no destination transaction yet, keep the original hash and use the service’s status page or support instructions to check the route. Avoid submitting the same transfer again just because the destination balance has not changed; a second attempt can create a separate transfer and charge another fee. The Bungee API includes a status endpoint for integrations, but occasional users can usually start with the transfer interface and the two explorers.

What should you do if the route appears stuck?

First identify the last confirmed stage. A failed source transaction means the transfer was not successfully submitted; a successful source transaction with no destination result points to processing or delivery; a successful destination transaction with no visible balance points to the wallet display, network selection, or token details.

Save the source hash, any destination hash, the route details, and the destination address. If the service offers a retry or recovery action, follow its instructions for that specific route and verify the destination address before signing anything. Do not send funds to an address supplied in an unsolicited message.

For a transfer you make only occasionally, save both transaction hashes until you have confirmed the right token arrived on the right network. That small habit makes it much easier to tell a slow route from a failed one.