<p>Blocks don't &quot;carry&quot; any unconfirmed transactions. By definition, a transaction is confirmed when it's included in a block.</p>
<p>Importantly, the block height when the transaction entered the mempool might be different from one mempool to another, as transactions take time to propagate through the network and a new block might be mined while it's propagating. It will also be different for transactions that your node receives from its peers when it's starting again after a downtime, since those transactions may have been in their mempool for many blocks already.</p>

CC BY-SA 4.0
2022-05-18T17:49:24.043Z
Thanks for this. Understood, blocks don't "carry" any unconfirmed transactions. But how then do transactions enter the mempool? I guess I am particularly confused by the mention of "the block height" when discussing transactions entering the mempool.
StatsScared
CC BY-SA 4.0
2022-05-19T22:23:27.430Z
@StatsScared Nodes relay transactions through the peer-to-peer network. To emphasize a point from my answer, there's no such thing as "the mempool", every node maintains its own mempool for storing received transactions that are waiting to be confirmed, and two mempools don't necessarily have the same transactions.
Vojtěch Strnad
CC BY-SA 4.0
2022-05-20T20:28:51.110Z
Thanks, @VojtěchStrnad. But I guess this make me wonder then. What is ‘the’ mempool references in sites like these: https://mempool.space/?
StatsScared
CC BY-SA 4.0
2022-05-20T22:47:06.133Z
@StatsScared Mempool explorers simply run their own Bitcoin node and offer its mempool for inspection. (mempool.space in particular is open source and you can easily run it over your own node, which removes trust and increases privacy.) Calling it 'the' mempool is just a simplification stemming from the fact that two nodes running the default mempool options and standardness policy will have very similar mempools.
Vojtěch Strnad
CC BY-SA 4.0
2022-05-31T00:17:46.630Z
I accepted this answer. But upon re-reading I can't help but notice that you said "By definition, a transaction is confirmed when it's included in a block." Isn't a confirmed transaction one that has been included in a block *and* added to the blockchain. Meaning that being included in a block is not sufficient to deem a transaction 'confirmed'?
StatsScared
CC BY-SA 4.0
2022-05-31T14:09:19.927Z
@StatsScared Yes, by "block" I don't mean just any block but specifically a block that is a part of the longest chain.
Vojtěch Strnad
CC BY-SA 4.0
2022-05-16T22:39:25.170Z
2022-05-16T22:39:25.170Z
Vojtěch Strnad
<p>I was tracking a transaction using a Bitcoin Core command. I was able to extract info on whether the transaction had entered the mempool.</p>
<p>Among the information I got were details such as &quot;the block height when the transaction entered the mempool&quot;.</p>
<p>Does this mean that blocks 'carry' unvalidated/unverified, but unconfirmed, transactions?</p>

<blockchain><unconfirmed-transactions><mempool>
How do transactions get into the mempool?
StatsScared
# How do transactions get into the mempool?

(Asked by: username_0 on 2022-05-16)

I was tracking a transaction using a Bitcoin Core command. I was able to extract info on whether the transaction had entered the mempool.

Among the information I got were details such as "the block height when the transaction entered the mempool".

Does this mean that blocks 'carry' unvalidated/unverified, but unconfirmed, transactions?

**Tags:** blockchain, unconfirmed-transactions, mempool


---

## 1 answers

### Answer by username_1 on 2022-05-16. Score: 5 | Accepted answer

Blocks don't "carry" any unconfirmed transactions. By definition, a transaction is confirmed when it's included in a block.

Importantly, the block height when the transaction entered the mempool might be different from one mempool to another, as transactions take time to propagate through the network and a new block might be mined while it's propagating. It will also be different for transactions that your node receives from its peers when it's starting again after a downtime, since those transactions may have been in their mempool for many blocks already.

> **Comments:**
> **username_0**: Thanks for this. Understood, blocks don't "carry" any unconfirmed transactions. But how then do transactions enter the mempool? I guess I am particularly confused by the mention of "the block height" when discussing transactions entering the mempool.  
> **username_1**: @username_0 Nodes relay transactions through the peer-to-peer network. To emphasize a point from my answer, there's no such thing as "the mempool", every node maintains its own mempool for storing received transactions that are waiting to be confirmed, and two mempools don't necessarily have the same transactions.  
> **username_0**: Thanks, @username_1. But I guess this make me wonder then. What is ‘the’ mempool references in sites like these: https://mempool.space/?  
> **username_1**: @username_0 Mempool explorers simply run their own Bitcoin node and offer its mempool for inspection. (mempool.space in particular is open source and you can easily run it over your own node, which removes trust and increases privacy.) Calling it 'the' mempool is just a simplification stemming from the fact that two nodes running the default mempool options and standardness policy will have very similar mempools.  
> **username_0**: I accepted this answer. But upon re-reading I can't help but notice that you said "By definition, a transaction is confirmed when it's included in a block." Isn't a confirmed transaction one that has been included in a block *and* added to the blockchain. Meaning that being included in a block is not sufficient to deem a transaction 'confirmed'?  
> **username_1**: @username_0 Yes, by "block" I don't mean just any block but specifically a block that is a part of the longest chain.  

---

