<p>This is an impossible question to answer, because there will likely be new transactions added to the mempool continuously. </p>

<ul>
<li><p>If more transactions get confirmed than are added, the mempool will shrink in size, and lower fee txs will confirm.</p></li>
<li><p>If less transactions get confirmed than are added, the mempool will grow in size, and it is likely that higher fee txs will confirm. </p></li>
</ul>

<p>As a user, the total number of transactions shouldn't be of concern to you, instead you should look at what the fee rates of currently confirming transactions are, and plan accordingly. If your tx needs to be confirmed ASAP, you should set a fee slightly higher than what you are currently seeing. If you can afford to wait, you can set the fee lower, and hope that the mempool will shrink in size (but this is fundamentally unpredictable, it depends on the actions of all other useres).</p>

<p>Ultimately, you'll really only care about the number of txs paying <em>a higher rate than you are willing to</em>. Those txs are the ones that will affect how long your tx takes to confirm. </p>

CC BY-SA 3.0
2018-01-15T06:20:23.467Z
2018-01-15T06:20:23.467Z
chytrik
<p>Blockchain.info says that right now (1/14/2018) there are approximately 42,000 transactions awaiting confirmation.  It also says that the average size of a block is 1,700.  If the target is 10 minutes per block, that suggests that there are roughly 4 hours of transactions yet to be confirmed.  If a transaction carries with it an "average fee", is it reasonable to assume that it will take approximately 4 hours for the first confirmation, and an hour more for 6 confirmations, given these numbers?  Is there any reasonable way to estimate how that time would change given a change in the fee (other than just accepting some website's recommended fee)?</p>

CC BY-SA 3.0
2018-01-16T15:13:03.593Z
For anyone interested in estimating fees, I found a good article that discusses some of the issues:  [The Challenges of Bitcoin Transaction Fee Estimation](https://blog.bitgo.com/the-challenges-of-bitcoin-transaction-fee-estimation-e47a64a61c72).
Randall Blake
<blockchain><unconfirmed-transactions><confirmation-time-estimation>
Can I estimate time to confirm based on the number of existing transactions awaiting confirmation?
Randall Blake
# Can I estimate time to confirm based on the number of existing transactions awaiting confirmation?

(Asked by: username_0 on 2018-01-15)

Blockchain.info says that right now (1/14/2018) there are approximately 42,000 transactions awaiting confirmation. It also says that the average size of a block is 1,700. If the target is 10 minutes per block, that suggests that there are roughly 4 hours of transactions yet to be confirmed. If a transaction carries with it an "average fee", is it reasonable to assume that it will take approximately 4 hours for the first confirmation, and an hour more for 6 confirmations, given these numbers? Is there any reasonable way to estimate how that time would change given a change in the fee (other than just accepting some website's recommended fee)?

**Tags:** blockchain, unconfirmed-transactions, confirmation-time-estimation

> **Comments:**
> **username_0**: For anyone interested in estimating fees, I found a good article that discusses some of the issues:  [The Challenges of Bitcoin Transaction Fee Estimation](https://blog.bitgo.com/the-challenges-of-bitcoin-transaction-fee-estimation-e47a64a61c72).  

---

## 1 answers

### Answer by username_1 on 2018-01-15. Score: 1 | Accepted answer

This is an impossible question to answer, because there will likely be new transactions added to the mempool continuously.

* If more transactions get confirmed than are added, the mempool will shrink in size, and lower fee txs will confirm.
* If less transactions get confirmed than are added, the mempool will grow in size, and it is likely that higher fee txs will confirm.

As a user, the total number of transactions shouldn't be of concern to you, instead you should look at what the fee rates of currently confirming transactions are, and plan accordingly. If your tx needs to be confirmed ASAP, you should set a fee slightly higher than what you are currently seeing. If you can afford to wait, you can set the fee lower, and hope that the mempool will shrink in size (but this is fundamentally unpredictable, it depends on the actions of all other useres).

Ultimately, you'll really only care about the number of txs paying *a higher rate than you are willing to*. Those txs are the ones that will affect how long your tx takes to confirm.


---

