<p>Yes, you are correct.<br>
In mempool = Unconfirmed.<br>
Blockchain = Confirmed.</p>

<p>A transaction with 1 input and 1 output is approximately 192 Bytes.<br>
Using 20 Sat/Byte will result in 0.0000384 BTC in transaction fees. However in real-life, <a href="https://charts.bitcoin.com/chart/transaction-size" rel="nofollow noreferrer">most transactions have more than 1 input and 1 output.</a> So on average the fees are much higher. </p>

<p>If you take a look at <a href="https://dedi.jochen-hoenicke.de/queue/#24h" rel="nofollow noreferrer">Johoe's Mempool Statistics</a>, you can tell that about 1/4 of the transactions in the mempool are sent with 50Sat/Byte or lower. These transactions will probably be stucked for a long time, or dropped gradually when they reach their <a href="https://github.com/bitcoin/bitcoin/commit/5f0e27f1a8495d9be43a953bd0371ccbce510105" rel="nofollow noreferrer">mempool expiry time(default 2 weeks for Bitcoin Core v0.14.0 and later)</a>.</p>

<blockquote>
  <p>Will this ever out-scale the number of miners on the network?</p>
</blockquote>

<p>Not in the sense that the network will go down, the target solve-time of a block is 10 minutes. <a href="https://bitcoin.stackexchange.com/questions/855/what-keeps-the-average-block-time-at-10-minutes">It doesn't matter if there are 10k miners or 10 million miners, the mining difficulty will over-time be adjusted so that the average block time approximate to 10 minutes given the total hash rate of the network.</a></p>

<p>At this rate, where there are more incoming transactions than what the network can process. The network will be more and more congested and eventually a lot of nodes mempool's will be saturated(if they have set a max cap), and new transactions will be rejected.</p>

CC BY-SA 3.0
2017-12-22T15:50:25.353Z
2017-12-22T15:50:25.353Z
Chak
<p>I see that blockchain.info is reporting a <a href="https://blockchain.info/unconfirmed-transactions" rel="nofollow noreferrer">large and steadily growing</a> number of unconfirmed transactions.</p>

<p>I assume that these are all transactions broadcasted to the network but never confirmed as a result of low fees.</p>

<p>What does this mean long-term? Given my understanding of the blockchain, only transactions on the blockchain are considered confirmed and don't exist on the blockchain if they are not confirmed - and instead, exist only in the mempool.</p>

<p>According to blockchain.info's <a href="https://blockchain.info/charts/mempool-size?timespan=all" rel="nofollow noreferrer">mempool size chart</a>, the mempool size has increased considerably since genesis, and some initial research shows that the size <em>does</em> grow with abnormal network conditions (high volume spikes, etc).</p>

<p>At the time of writing, the number of transactions is 285,565, totaling about 228.71450055 BTC that are tied up in fees.</p>

<p>That means about 0.0008009192322 BTC per transaction on average. However, following the rule of 20 satoshis per byte, on average, each transaction would need only 0.00002 BTC in fees - about <strong>40 times</strong> less than what is currently tied up in BTC fees.</p>

<p>What's going on here? Will the number of unconfirmed transactions die down over time? Will it increase uncontrollably? Will this ever out-scale the number of miners on the network?</p>

<p>Or am I completely missing something here?</p>

CC BY-SA 3.0
2017-12-22T05:02:20.017Z
Bitcoin is limited to about 15,000 transactions per hour.  The number of transactions will go down over time, but anytime people are adding transactions faster than 15,000 / hour, the network cannot keep up and the backlog will grow.
abelenky
<unconfirmed-transactions><scalability><mempool>
Why is Bitcoin's unconfirmed transaction count rising and what effect does it have on the network?
Qix - MONICA WAS MISTREATED
# Why is Bitcoin's unconfirmed transaction count rising and what effect does it have on the network?

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

I see that blockchain.info is reporting a [large and steadily growing](https://blockchain.info/unconfirmed-transactions) number of unconfirmed transactions.

I assume that these are all transactions broadcasted to the network but never confirmed as a result of low fees.

What does this mean long-term? Given my understanding of the blockchain, only transactions on the blockchain are considered confirmed and don't exist on the blockchain if they are not confirmed - and instead, exist only in the mempool.

According to blockchain.info's [mempool size chart](https://blockchain.info/charts/mempool-size?timespan=all), the mempool size has increased considerably since genesis, and some initial research shows that the size *does* grow with abnormal network conditions (high volume spikes, etc).

At the time of writing, the number of transactions is 285,565, totaling about 228.71450055 BTC that are tied up in fees.

That means about 0.0008009192322 BTC per transaction on average. However, following the rule of 20 satoshis per byte, on average, each transaction would need only 0.00002 BTC in fees - about **40 times** less than what is currently tied up in BTC fees.

What's going on here? Will the number of unconfirmed transactions die down over time? Will it increase uncontrollably? Will this ever out-scale the number of miners on the network?

Or am I completely missing something here?

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

> **Comments:**
> **username_1**: Bitcoin is limited to about 15,000 transactions per hour.  The number of transactions will go down over time, but anytime people are adding transactions faster than 15,000 / hour, the network cannot keep up and the backlog will grow.  

---

## 1 answers

### Answer by username_2 on 2017-12-22. Score: 1

Yes, you are correct.  
In mempool = Unconfirmed.  
Blockchain = Confirmed.

A transaction with 1 input and 1 output is approximately 192 Bytes.  
Using 20 Sat/Byte will result in 0.0000384 BTC in transaction fees. However in real-life, [most transactions have more than 1 input and 1 output.](https://charts.bitcoin.com/chart/transaction-size) So on average the fees are much higher.

If you take a look at [Johoe's Mempool Statistics](https://dedi.jochen-hoenicke.de/queue/#24h), you can tell that about 1/4 of the transactions in the mempool are sent with 50Sat/Byte or lower. These transactions will probably be stucked for a long time, or dropped gradually when they reach their [mempool expiry time(default 2 weeks for Bitcoin Core v0.14.0 and later)](https://github.com/bitcoin/bitcoin/commit/5f0e27f1a8495d9be43a953bd0371ccbce510105).

> Will this ever out-scale the number of miners on the network?

Not in the sense that the network will go down, the target solve-time of a block is 10 minutes. [It doesn't matter if there are 10k miners or 10 million miners, the mining difficulty will over-time be adjusted so that the average block time approximate to 10 minutes given the total hash rate of the network.](https://bitcoin.stackexchange.com/questions/855/what-keeps-the-average-block-time-at-10-minutes)

At this rate, where there are more incoming transactions than what the network can process. The network will be more and more congested and eventually a lot of nodes mempool's will be saturated(if they have set a max cap), and new transactions will be rejected.


---

