What is the real number of unconfirmed transactions?

[MirkoIta]

I usually check http://bitcointicker.co/networkstats/ to see how many TXs are in the mempool before I send a transaction.

I'm wondering since a while, why does https://blockchain.info/unconfirmed-transactions show 58,000 when there are "only" 17,000 in the mempool (as shown on bitcointicker)? Where does blockchain.info pull out those 40,000 more unconfirmed transactions?

[mocacinno]

I usually check http://bitcointicker.co/networkstats/ to see how many TXs are in the mempool before I send a transaction.

I'm wondering since a while, why does https://blockchain.info/unconfirmed-transactions show 58,000 when there are "only" 17,000 in the mempool (as shown on bitcointicker)? Where does blockchain.info pull out those 40,000 more unconfirmed transactions?

I'm just guessing here, but there are several possibilitys:
they have different configuration...

Code:

-maxmempool=<n>	Keep the transaction memory pool below <n> megabytes (default: 300)
-mempoolexpiry=<n>	Do not keep transactions in the mempool longer than <n> hours (default: 72)

* source: https://en.bitcoin.it/wiki/Running_Bitcoin

OR, they might have restarted their node, clearing their mempool

[kiklo]

https://themerkle.com/bitcoin-experiencing-network-delays-what-to-do/

The main issue the Bitcoin network is experiencing right now is a backlog to it’s Mempool (memory pool). The Mempool is a set amount of storage space that each Bitcoin node has that serves as a holding cell for pending transactions. The nodes receive transactions from the network constantly, and after a brief verification that the hashes match up and the transaction is valid they hold it in memory before a miner picks it up. As soon as the miner finds and a block, each node compares the transactions in the block vs the ones in it’s Mempool, it then removes the confirmed txs from it’s memory.

The Mempool is constantly changing as transactions are appended and removed from it. In the case of an overflow, too many transactions flow in the mempool causing a backlog.
Since different nodes have a different size allocated to the mempool, they each set their own threshold for the minimum transaction fee. Since the real backlog is memory and not amount of transactions, the fee is set per byte, not per transaction. Any transactions not containing a high enough fee / byte, will be automatically dropped from memory, effectively going to limbo. The good news is since the transaction never confirms, the protocol doesn’t see that you sent bitcoins to a certain address, so you are still in possession of your coins. Recovering them is a different story and depends on your wallet solution.

Only ~ 5000 difference between these two.
https://blockchain.info/unconfirmed-transactions
https://tradeblock.com/bitcoin/

 

[MirkoIta]

Thanks for the replies, I suppose it's something about different configuration. I usually check both blockchain and bitticker when I read doom talks, bitcoin is ded, 100k unconfirmed and there are usually between 20k and 40k more shown on the first.

I usually check http://bitcointicker.co/networkstats/ to see how many TXs are in the mempool before I send a transaction.

I'm wondering since a while, why does https://blockchain.info/unconfirmed-transactions show 58,000 when there are "only" 17,000 in the mempool (as shown on bitcointicker)? Where does blockchain.info pull out those 40,000 more unconfirmed transactions?

I'm just guessing here, but there are several possibilitys:
they have different configuration...

Code:

-maxmempool=<n>	Keep the transaction memory pool below <n> megabytes (default: 300)
-mempoolexpiry=<n>	Do not keep transactions in the mempool longer than <n> hours (default: 72)

* source: https://en.bitcoin.it/wiki/Running_Bitcoin

OR, they might have restarted their node, clearing their mempool

https://themerkle.com/bitcoin-experiencing-network-delays-what-to-do/

The main issue the Bitcoin network is experiencing right now is a backlog to it’s Mempool (memory pool). The Mempool is a set amount of storage space that each Bitcoin node has that serves as a holding cell for pending transactions. The nodes receive transactions from the network constantly, and after a brief verification that the hashes match up and the transaction is valid they hold it in memory before a miner picks it up. As soon as the miner finds and a block, each node compares the transactions in the block vs the ones in it’s Mempool, it then removes the confirmed txs from it’s memory.

The Mempool is constantly changing as transactions are appended and removed from it. In the case of an overflow, too many transactions flow in the mempool causing a backlog.
Since different nodes have a different size allocated to the mempool, they each set their own threshold for the minimum transaction fee. Since the real backlog is memory and not amount of transactions, the fee is set per byte, not per transaction. Any transactions not containing a high enough fee / byte, will be automatically dropped from memory, effectively going to limbo. The good news is since the transaction never confirms, the protocol doesn’t see that you sent bitcoins to a certain address, so you are still in possession of your coins. Recovering them is a different story and depends on your wallet solution.

Only ~ 5000 difference between these two.
https://blockchain.info/unconfirmed-transactions
https://tradeblock.com/bitcoin/

 

[bitbunnny]

I don't know where this data come from but since all transactions are registered there must be some source. Maybe this number are overal transactions that are in process of confirmations.  It's already been disccused that there are many unconfirmed transactions, like the number is increasing.

[MirkoIta]

I don't know where this data come from but since all transactions are registered there must be some source. Maybe this number are overal transactions that are in process of confirmations.  It's already been disccused that there are many unconfirmed transactions, like the number is increasing.

I know it's already been discussed since months but there is something wrong with it.In the past 2 days I made 8 transactions with a fee between 16k and 35k sats and all of them got included in the next 1 or 2 blocks. I think it has something to do with someone pushing the idea that the Bitcoin network is broken.

[Kprawn]

They are definitely forcing the issue with this latest spam attack and you can see these people know what they are targeting and how

effective this is. It is a damn shame that someone can do this, and not think of the real damage that this is doing. { New merchants and

potential new Bitcoin users, experiencing this and waiting for 24 to 36 hours for confirmations. } @!#$%^$^%^%^!!!!!

[DannyHamilton]

- snip -
how many TXs are in the mempool
- snip -

There is no such thing as "THE mempool"

Every node has it's own mempool.  Transactions that one node has in it's mempool, might not be in another node's mempool.  There is nothing in the protocol that requires any nodes to keep any particular number of transactions in their mempool or to keep the transactions there for any particular amount of time.  If you are checking two different sources, your are going to get the results based on how each mempool is configured.

- snip -
since all transactions are registered
- snip -

Registered where?  Please don't make up nonsense and post it when you don't know what you're talking about, you'll confuse the newbies that don't realize that you're just trying to increase your post count for your advertiser.

[MirkoIta]

There is no such thing as "THE mempool"

Every node has it's own mempool.  Transactions that one node has in it's mempool, might not be in another node's mempool.  There is nothing in the protocol that requires any nodes to keep any particular number of transactions in their mempool or to keep the transactions there for any particular amount of time.  If you are checking two different sources, your are going to get the results based on how each mempool is configured.

I really thought there was a single mempool shared with all the nodes,so thank you for explaining that to me.