<p>Every Bitcoin node creates it's own blockchain. When a new block is found, it is broadcasted to the network. Other nodes will only consider the highest blockchain as being the "real" blockchain. </p>

<p>Sometimes, two separate nodes build a block containing different transactions. Two competing blockchains now exist, it is now a race for the next block. Once the next block is found, we can reject the other inferior chain. But if that inferior blockchain manages to get two new blocks, it will be broadcasted again as the main one. </p>

<p>To avoid having a transaction that was once in a block, but it got replaced, we simply state how many blocks happened since the transaction as confirmations. After 6 confirmation it's considered almost impossible to alter, so we just say it's confirmed.</p>

CC BY-SA 3.0
2017-12-22T20:28:24.590Z
Thanks for this detailed explanation.  A follow-up, if the scenario happens taht you described in paragraph 2 -- the inferior blockchain manages to get two new blocks, thus becoming the main chain -- is there any affect on the people involved in the transaction that was once part of a different chain but is now part of this new one?
Dave
CC BY-SA 3.0
2017-12-22T20:31:14.063Z
Yes, transactions which may have not existed now exist and transactions which were confirmed in earlier blocks may seem like they never happened. This is why you should always wait 6 confirmations with Bitcoin
Cedric Martens
CC BY-SA 3.0
2017-12-22T20:33:04.147Z
You can check orphaned blocks here : https://blockchain.info/orphaned-blocks
Cedric Martens
CC BY-SA 4.0
2018-07-23T01:21:11.743Z
Aside, the blockchain.info orphaned blocks list no longer seems to work. It never managed to catch all the orphans but now it seems to catch almost none of them.
G. Maxwell
CC BY-SA 4.0
2017-12-21T04:15:39.937Z
2018-10-03T21:21:56.353Z
2018-10-03T21:21:56.353Z
Cedric Martens
<p>After a transaction is confirmed and included in a block, it is said to have a depth (confirmation) of one.  However I've read that many companies require &quot;multiple&quot; confirmations (up to 6) before they consider a transaction truly confirmed.  Does that mean that a block that is confirmed can be revoked, thus nullifying the previously confirmed transaction?  What purpose would such a behavior serve -- in other words, once a transaction is confirmed and a block is formed, what advantage is there to later &quot;unconfirmed&quot; that block?</p>

CC BY-SA 3.0
2017-12-21T03:09:31.240Z
related: https://bitcoin.stackexchange.com/q/48302/5406, https://bitcoin.stackexchange.com/q/29911/5406, https://bitcoin.stackexchange.com/a/44407/5406, https://bitcoin.stackexchange.com/q/13987/5406
Murch
CC BY-SA 3.0
2017-12-21T03:22:10.577Z
Perhaps due to my novice understanding of how this all works, I don't see how the above is related to my question.
Dave
CC BY-SA 3.0
2017-12-22T20:30:12.217Z
I'm afraid you're right: What you're describing is a chain reorganization, i.e. an event where a blockchain tip becomes stale due to being overtaken by a competing blockchain tip. All four linked questions describe aspects of this event that relate to your question in some fashion.
Murch
<blockchain><confirmations><chain-reorganization>
Why is the Bitcoin blockchain designed so that a block can be unconfirmed?
Dave
# Why is the Bitcoin blockchain designed so that a block can be unconfirmed?

(Asked by: username_0 on 2017-12-21)

After a transaction is confirmed and included in a block, it is said to have a depth (confirmation) of one. However I've read that many companies require "multiple" confirmations (up to 6) before they consider a transaction truly confirmed. Does that mean that a block that is confirmed can be revoked, thus nullifying the previously confirmed transaction? What purpose would such a behavior serve -- in other words, once a transaction is confirmed and a block is formed, what advantage is there to later "unconfirmed" that block?

**Tags:** blockchain, confirmations, chain-reorganization

> **Comments:**
> **username_1**: related: https://bitcoin.stackexchange.com/q/48302/5406, https://bitcoin.stackexchange.com/q/29911/5406, https://bitcoin.stackexchange.com/a/44407/5406, https://bitcoin.stackexchange.com/q/13987/5406  
> **username_0**: Perhaps due to my novice understanding of how this all works, I don't see how the above is related to my question.  
> **username_1**: I'm afraid you're right: What you're describing is a chain reorganization, i.e. an event where a blockchain tip becomes stale due to being overtaken by a competing blockchain tip. All four linked questions describe aspects of this event that relate to your question in some fashion.  

---

## 1 answers

### Answer by username_2 on 2017-12-21. Score: 3 | Accepted answer

Every Bitcoin node creates it's own blockchain. When a new block is found, it is broadcasted to the network. Other nodes will only consider the highest blockchain as being the "real" blockchain.

Sometimes, two separate nodes build a block containing different transactions. Two competing blockchains now exist, it is now a race for the next block. Once the next block is found, we can reject the other inferior chain. But if that inferior blockchain manages to get two new blocks, it will be broadcasted again as the main one.

To avoid having a transaction that was once in a block, but it got replaced, we simply state how many blocks happened since the transaction as confirmations. After 6 confirmation it's considered almost impossible to alter, so we just say it's confirmed.

> **Comments:**
> **username_0**: Thanks for this detailed explanation.  A follow-up, if the scenario happens taht you described in paragraph 2 -- the inferior blockchain manages to get two new blocks, thus becoming the main chain -- is there any affect on the people involved in the transaction that was once part of a different chain but is now part of this new one?  
> **username_2**: Yes, transactions which may have not existed now exist and transactions which were confirmed in earlier blocks may seem like they never happened. This is why you should always wait 6 confirmations with Bitcoin  
> **username_2**: You can check orphaned blocks here : https://blockchain.info/orphaned-blocks  
> **username_3**: Aside, the blockchain.info orphaned blocks list no longer seems to work. It never managed to catch all the orphans but now it seems to catch almost none of them.  

---

