A phone disconnect does not stop a swap already sent
A disconnected phone cannot stop a swap already broadcast to a blockchain; the wait depends on network inclusion, while an unsigned request has not begun.
Web3 News Editorial2 min read

A swap that has already been broadcast can complete after your phone disconnects; it takes however long the network needs to include and confirm it. Ethereum.org’s transaction documentation says a submitted transaction enters the network’s pending pool, then a validator includes it in a block; losing the app connection does not withdraw it.
Does a swap keep running if your phone goes offline?
Yes, if you signed and submitted the transaction before the disconnection. Ethereum.org explains that a signed transaction is broadcast to the network for execution, so the phone and swap app are no longer needed for that on-chain step.
If you had only opened the swap screen or were still approving it in your wallet, no transaction may have been sent. Ethereum.org identifies signing and submission as steps in the transaction process; without a transaction hash or matching entry in a block explorer, the swap may not have started.
How can you tell whether the swap is finished?
Look up the transaction hash in a block explorer for the network you used. Ethereum.org says the hash is generated when a transaction is submitted, and that a validator must include it in a block for it to count as successful.
- Pending: the transaction has been submitted but is not yet included in a block.
- Successful: the block explorer reports that execution succeeded; check your wallet balance for the output token.
- Failed: the record shows execution did not complete; check the transaction details before trying again.
Network congestion and the fee offered can affect how quickly a pending transaction is included, Ethereum.org notes in its transaction and gas documentation. A single-chain token swap is one on-chain transaction; a bridge route can require additional steps on another network, so its total wait depends on that route too.
What should you do after a disconnect?
First, find the transaction hash in your wallet’s activity or check the address on the relevant block explorer; use that record to decide whether to wait or act. If no transaction appears, reconnect your wallet and check whether it still needs your approval.
For a Bitcoin-to-Ethereum route, QuickSwap Bitcoin-to-Ethereum bridging steps cover the route details. The next update should come from the network record, but until it appears the final status and, for a bridge, destination-side delivery remain unconfirmed.