A BTC-to-ETH swap often takes tens of minutes, with the Bitcoin deposit usually controlling the first wait; the total depends on how many confirmations the route requires and current network conditions. For a first-time user, the key distinction is whether Bitcoin is still unconfirmed or the swap has begun sending ETH.
Bitcoin confirmations set the first checkpoint
A Bitcoin transaction gets its first confirmation when a miner includes it in a block. Bitcoin blocks arrive about every 10 minutes on average, but that is not a countdown: the next block can arrive sooner or take much longer. A low transaction fee during a busy period can also leave your payment waiting in the queue.
The swap route may require more than one confirmation before it treats your BTC deposit as ready. That requirement is a security threshold: each added block makes it harder for a transaction to be reversed, but adds another uncertain wait. The Bitcoin Developer Guide says a transaction with a sufficient fee takes 10 minutes on average to receive one confirmation; the route’s confirmation policy determines whether one is enough.
For example, if your BTC transaction appears in an explorer with zero confirmations, it has been broadcast but is not yet in a block. If it has one confirmation but the swap has not advanced, the route may be waiting for more. In a thor swap, that source-chain checkpoint can account for most of the time you spend waiting.
The swap has a second clock on Ethereum
Once the route accepts the Bitcoin deposit, it still has to complete the cross-chain exchange and send ETH to your destination address. In general, a cross-chain service monitors the deposit, acts on the swap, then broadcasts a separate transaction on the destination chain. Those are distinct events, so seeing BTC confirmed does not mean ETH has already arrived.
Ethereum adds its own timing. Ethereum.org describes slots as 12 seconds apart, but a transaction being included in a block is different from being finalized, the point at which the network treats it as settled. The service may wait for its chosen safety threshold before marking the destination leg complete, so the ETH leg can add time even when Ethereum is producing blocks normally.
If you want to move BTC into ETH without managing each cross-chain step separately, the thor swap service handles the move as one cross-chain swap flow. Its timing still depends on the source deposit and destination settlement, so a single flow does not mean an instant one.
At thorswap.us, you can put a BTC-to-ETH move through one cross-chain flow instead of arranging the chain-to-chain steps yourself.
Check the transaction state before acting
Use the Bitcoin transaction ID, or txid, to check whether your deposit is unconfirmed or has entered a block. Then compare that state with the swap’s displayed progress: the useful question is whether the BTC leg is still waiting for confirmations or the destination ETH leg is underway. A thor swap can appear stalled between those stages even though the source transaction is already confirmed.
If BTC is still unconfirmed, the wait is on Bitcoin; broadcasting another payment can create a second deposit. If BTC has the required confirmations but ETH has not arrived, the route is processing the next leg. Check the ETH transaction on an Ethereum block explorer once one is shown, and confirm that you are checking the destination address you intended to use.
When estimating thor swap timing, plan for a Bitcoin confirmation wait plus the separate time needed to settle the ETH transfer; the confirmation count and live network conditions decide the actual wait.