Skip to main content
Coinvane

News from across crypto

Switching Networks Won’t Move a Pending Swap

Switching networks changes the wallet’s active chain, but it does not move a submitted swap; check the original chain before retrying or replacing it.

The Coinvane Desk3 min read

Abstract cover artwork

Switching networks in your wallet does not move a submitted swap to the new chain; it only changes which chain the wallet and app are showing. That matters because a swap sent on one network must be checked, completed or replaced on that same network. A network switch alone does not cancel it.

What does “pending” mean during a swap?

“Pending” can describe two different stages. Before you approve a wallet prompt, the swap may only be waiting for your signature; no transaction has been sent yet. After you sign and submit it, the transaction is broadcast to the chosen network and waits to be included in a block. Ethereum’s transaction documentation describes this waiting pool as the transaction pool. The word “pending” in a wallet or swap app may refer to either stage, so check whether you have a transaction hash.

A swap may also require a separate token approval first. An approval gives a contract permission to use a token, while the swap is a later transaction. For a closer look at what to inspect before signing an approval, see our guide to blackhole swap. The approval and swap can each have their own status.

What changes when you switch networks?

Your wallet changes its active network, and the app may refresh to show that network’s balances and activity. The submitted transaction remains tied to its original chain. Ethereum-compatible networks can share an address format, but that does not make their transaction histories or balances interchangeable. A swap submitted on one chain will not execute on another just because the wallet now displays it.

The app may stop showing the old swap, show a network mismatch, or ask you to switch back. That is a display or connection issue; it does not tell you whether the transaction succeeded. Some routes involve several steps, such as a swap followed by a bridge. In those cases, a later step may wait for the earlier one to confirm. Uniswap’s documentation describes these as ordered steps, with the next action becoming ready after the previous one completes.

How can you check or resolve the pending swap?

Return to the network where you started and check the transaction hash in that chain’s block explorer, a site that displays on-chain activity. If there is no hash, look in the wallet for a waiting signature or confirmation. If there is a hash, the explorer can show whether the transaction is pending, confirmed or failed. MetaMask’s guidance also distinguishes a transaction that has reached the network from one still waiting in the wallet.

  • If it is awaiting your signature, review the chain and transaction details before approving or rejecting it.
  • If it was submitted, check its status on the original network before trying the swap again.
  • If it remains pending, wallet options to speed it up or cancel it may be available. MetaMask says these actions work by submitting a replacement transaction with the same nonce, a per-account transaction counter.
  • If a swap step completed but the next has not started, return to the app and check its status on the chain required for that next step.

For most readers, the simplest move is to keep the wallet on the originating network until the transaction’s status is clear. Switching back can help the app and wallet show the right context, but it cannot reverse a confirmed transaction. If the swap failed, review the reason before submitting another one; if it succeeded, check the destination token balance on the chain where it was sent.