What Happens to Your Transaction During a Chain Reorganization?
When a blockchain reorganizes, your transaction can switch from confirmed to unconfirmed, disappear from the chain entirely, or end up in a different block with a different status. A chain reorganization - often called a reorg - is a rare but normal event where the network discards one or more blocks and replaces them with a different set. Your transaction's fate depends on whether it was included in the discarded blocks and whether the replacement blocks also include it.
What causes a chain reorg
Blockchains aim for a single, canonical chain of blocks. Miners or validators propose blocks roughly at the same time. The network temporarily sees two competing chains. Eventually one chain grows longer, and the shorter chain is abandoned. That abandonment is the reorg.
Reorgs happen for several reasons:
- Network latency. Two valid blocks arrive at different nodes nearly simultaneously. The chain that gets the next block first wins.
- Deliberate attacks. An entity with enough hash power or staked capital mines or validates a private chain, then releases it to replace the public chain. This is rare on major proof-of-work chains and harder on proof-of-stake chains with finality mechanisms.
- Client bugs or consensus failures. A software bug can cause nodes to temporarily disagree about which block is valid.
Most reorgs on Bitcoin and Ethereum are one or two blocks deep. Deeper reorgs are increasingly unlikely as more blocks are built on top.
What happens to your transaction during a reorg
If your transaction was in a discarded block
The block that contained your transaction is no longer part of the canonical chain. The network treats your transaction as if it never happened. Your wallet balance returns to its pre-transaction state. The transaction appears as "pending" or disappears from explorers that follow the canonical chain.
If your transaction was not in the discarded block
Nothing changes. Your transaction remains confirmed in blocks that stay on the canonical chain.
If your transaction is re-included in the replacement chain
Miners or validators building the replacement blocks may re-include your transaction if it was still in the mempool and the gas price was competitive. If the replacement chain's blocks are full or your transaction was dropped from the mempool, it may never appear again. You would need to resubmit it.
If your transaction conflicts with a transaction in the replacement chain
A reorg can expose a double-spend attempt. If you sent the same coins in two different transactions, only one survives. The other is permanently invalid. For normal users, this is extremely rare. For exchanges and services that accept zero-confirmation transactions, a reorg can cause the receiving transaction to vanish.
How to check if a reorg affected your transaction
You can use a block explorer to see whether the block containing your transaction still exists.
- Find the block number of your transaction in an explorer like Etherscan, Blockchair, or Mempool.space.
- Check the current chain tip. Compare the block number to the latest block. If your block is more than six blocks deep on Bitcoin or more than 32 epochs deep on Ethereum proof-of-stake, a reorg is extremely unlikely.
- Look for orphaned blocks. Some explorers label blocks as "uncle" (Ethereum proof-of-work) or "orphan." If your transaction's block is listed as orphaned, it was discarded.
- Search for your transaction hash directly. If the explorer returns "transaction not found" or shows it as pending, the reorg may have removed it. Wait for the replacement chain to stabilize. Then resubmit if needed.
How long until you can be sure a reorg won't affect you
Confidence increases with block depth. On Bitcoin, most services require six confirmations (roughly one hour) before considering a transaction final. On Ethereum proof-of-stake, the Casper finality gadget finalizes blocks after two epochs (about 13 minutes). Once a block is finalized, a reorg would require a massive coordinated attack that slashes a third of all staked ETH.
For most users, a single confirmation on a major chain is safe for small amounts. For large transfers, wait for the standard confirmation threshold of the service you are using.
What to do if your transaction disappears
- Wait. The network may resolve the reorg within minutes. Do not resubmit immediately.
- Check your wallet. If the transaction is gone and your balance has returned to the pre-transaction state, the reorg removed it.
- Resubmit the transaction with the same or higher gas price. Your wallet should handle this automatically. If not, create a new transaction with the same details.
- If the transaction was a time-sensitive trade, the price may have moved. Reevaluate before resubmitting.
Tools that help you monitor reorgs
Block explorers show orphaned blocks. Analytics platforms like Dune or Nansen may surface reorg events in their chain health dashboards. For real-time alerts, some node monitoring services track chain depth and notify you when a reorg exceeds a certain threshold.
What reorgs mean for on-chain analysis
A reorg can temporarily confuse wallet labeling, balance tracking, and event log queries. If you are pulling data from an explorer API or a Dune query, your results may include transactions that were later reorged. Most explorers and analytics tools eventually prune orphaned data, but there is a window where stale data can affect your analysis. Always check block depth before treating a transaction as final.
Not financial advice. basiliskawakens.xyz publishes market data and general information about digital assets. Crypto assets are volatile and you can lose everything you put in. Nothing here is a recommendation to buy, sell or hold, and we make no price predictions.
Prices are sourced from third parties and may be delayed or wrong. Verify anything you intend to act on against a primary source.