<p>Mempools between nodes will be different. There is no "supposed to match after a while" as the mempool does not have anything that makes all nodes' mempools converge to the same thing. There is no "the mempool", there is only "a node's mempool" and these will differ based on the settings for accepting transactions.</p>

<p>The settings on your node's mempool are likely much stricter than the settings for blockchain.info's mempool since blockchain.info shows data for a variety of transactions that most nodes will reject (e.g. transaction fees less than 1000 sat/kB, creating dust outputs, unconfirmed transaction chains longer than 20 txs, etc.).</p>

CC BY-SA 3.0
2017-10-02T15:10:22.997Z
2017-10-02T15:10:22.997Z
Ava Chow
<p>It's supposed to match after a while. When several bitcoin nodes are running for days they should have the same mempool, but my bitcoind node shows arround 2k transactions less than blockchain.info webpage. My mempool size limit is 300Mb and at the moment of writing is arround 16Mb. Why is this happening?</p>

<mempool>
Why my bitcoin node does not show the same mempool size than a web blockexplorer?
dev7ba
# Why my bitcoin node does not show the same mempool size than a web blockexplorer?

(Asked by: username_0 on 2017-10-02)

It's supposed to match after a while. When several bitcoin nodes are running for days they should have the same mempool, but my bitcoind node shows arround 2k transactions less than blockchain.info webpage. My mempool size limit is 300Mb and at the moment of writing is arround 16Mb. Why is this happening?

**Tags:** mempool


---

## 1 answers

### Answer by username_1 on 2017-10-02. Score: 1 | Accepted answer

Mempools between nodes will be different. There is no "supposed to match after a while" as the mempool does not have anything that makes all nodes' mempools converge to the same thing. There is no "the mempool", there is only "a node's mempool" and these will differ based on the settings for accepting transactions.

The settings on your node's mempool are likely much stricter than the settings for blockchain.info's mempool since blockchain.info shows data for a variety of transactions that most nodes will reject (e.g. transaction fees less than 1000 sat/kB, creating dust outputs, unconfirmed transaction chains longer than 20 txs, etc.).


---

