If your browser disconnects during a cross-chain swap, check the transaction on the source blockchain before doing anything again. A confirmed transaction can keep moving after you close the page; the key is to find its record and check whether the tokens arrived on the destination blockchain.
Start with the transaction on the source chain
A browser disconnect does not cancel a transaction that the blockchain has already accepted. The source chain is the network where your tokens started, and its transaction record tells you whether the swap request was sent, is still waiting, or failed.
Open your wallet’s activity or history and find the transaction from around the time of the swap. If you see a transaction hash, copy it; this long string of letters and numbers identifies that transaction. Search for it in the source chain’s block explorer, a website that displays public blockchain records.
Look for its status. “Pending” means the network has not finished processing it, “success” means the source transaction completed, and “reverted” or “failed” means it did not complete as requested. A successful source transaction does not always mean the destination tokens have arrived: the cross-chain part may still be running.
Follow the transfer from source to destination
A cross-chain transfer usually has more than one stage. First, the source chain records your request; then a bridge or messaging system carries proof of that request to the destination chain, where a separate transaction releases or swaps the tokens. Chainlink CCIP’s documentation describes a similar send, verify, and execute sequence.
For a transfer using an intent, the path can differ: an intent is a request for a particular result, which a relayer may complete by sending tokens on the destination chain. Across describes this kind of approach. In either design, look for a message ID or destination transaction hash in the transaction details, a service’s status record, or a supported cross-chain explorer.
Here are two common cases. If the source transaction is still pending, wait and check it again; if it reverted, there is no completed transfer to track. If it succeeded but the destination transaction is missing, the request may still be waiting for confirmation or delivery, so check the message status before trying again.
Check the result before repeating the swap
When the destination transaction appears, open it in the destination chain’s explorer and check whether it succeeded. Then check your wallet on that same chain for the token you expected. Token names can look alike, so compare the token’s contract address—the public identifier for that specific token—if the balance is unclear.
A status such as “pending” or “in progress” usually means the transfer has not reached its final step. Some routes take longer because they wait for source-chain confirmations, which are blocks added after the transaction and used to reduce the risk of a chain changing its recent history. A missing record immediately after sending can also mean the tracking service has not indexed it yet.
For a general route that moves or swaps tokens between chains, omnichain is one service to consider. The omnichain status you see still needs to be checked against the source and destination records, because a page can lose connection while the transfer continues.
omnichain.network is a service for moving and swapping tokens across multiple blockchains from one interface. You can use the same recovery checks with any cross-chain service: the source transaction shows whether the request began, and the destination record shows whether it finished.
Keep these details before you close the page
In practice, I check the source record first and only retry when it confirms the original request failed. Repeating a swap while the first one is still moving can send a second transfer, which may cost extra network fees and leave you with more tokens than intended.
Before you finish, make sure you have:
- The source-chain name and transaction hash.
- The current source transaction status.
- The message ID or destination transaction hash, if available.
- A successful destination record and the expected token balance.
Top comments (0)