Topic: Mempool size falling to 0 : what's going on ? (Read 875 times)
Blockchain has a time delay of ~two minutes for showing new blocks in the log. BTC.com provides better results than Blockchain.info does and they listed all important stats on the first page.
thank you for clarifying, I will look up for a better explorer.
Blockchain.info is the most famous but is a very good option for me
Blockchain.info is the most famous but is a very good option for me
That does not look natural. That is almost certainly because of problems that blockchain.info has. It doesn't match what other mempool chart sites like https://jochen-hoenicke.de/queue/#2d show.
Blockchain.info is notorious for providing outdated information or delayed information. I do not even use it as a Block explorer anymore, because it is very unreliable. I have done transactions and monitored it with both Blockchain.info and Blockexplorer.com and 90% of the time, Blockexplorer.com will be more accurate than Blockchain.info.
How many other people experience the same problems with Blockchain.info? Do the test and see for yourself. ^smile^
Can you check the mempool size at Blockexplorer.com ? How many other people experience the same problems with Blockchain.info? Do the test and see for yourself. ^smile^
Blockchain.info is notorious for providing outdated information or delayed information. I do not even use it as a Block explorer anymore, because it is very unreliable. I have done transactions and monitored it with both Blockchain.info and Blockexplorer.com and 90% of the time, Blockexplorer.com will be more accurate than Blockchain.info.
How many other people experience the same problems with Blockchain.info? Do the test and see for yourself. ^smile^
How many other people experience the same problems with Blockchain.info? Do the test and see for yourself. ^smile^
The data that you see is not a representation of what everyone else sees. The data that you see is solely based on the number of transactions Blockchain.info has on their mempool, everyone can have different numbers due to poor propagation of transactions or differing rules.
The drop in the mempool transactions is likely triggered by a restart of the nodes that they have. The mempool might have been emptied by Blockchain.info and the increase in the number of transactions is due to nodes sending more transaction data to Blockchain.info after that.
The drop in the mempool transactions is likely triggered by a restart of the nodes that they have. The mempool might have been emptied by Blockchain.info and the increase in the number of transactions is due to nodes sending more transaction data to Blockchain.info after that.
It is interesting that they are running a pre-0.14.0 Bitcoin Core or they have the save mempool feature disabled. Or the had an unclean shutdown.
The data that you see is not a representation of what everyone else sees. The data that you see is solely based on the number of transactions Blockchain.info has on their mempool, everyone can have different numbers due to poor propagation of transactions or differing rules.
The drop in the mempool transactions is likely triggered by a restart of the nodes that they have. The mempool might have been emptied by Blockchain.info and the increase in the number of transactions is due to nodes sending more transaction data to Blockchain.info after that.
Thank you for these explaination.The drop in the mempool transactions is likely triggered by a restart of the nodes that they have. The mempool might have been emptied by Blockchain.info and the increase in the number of transactions is due to nodes sending more transaction data to Blockchain.info after that.
It is most clear in my mind now, specialy the restart of the blockchain.info node :-).
The data that you see is not a representation of what everyone else sees. The data that you see is solely based on the number of transactions Blockchain.info has on their mempool, everyone can have different numbers due to poor propagation of transactions or differing rules.
The drop in the mempool transactions is likely triggered by a restart of the nodes that they have. The mempool might have been emptied by Blockchain.info and the increase in the number of transactions is due to nodes sending more transaction data to Blockchain.info after that.
The drop in the mempool transactions is likely triggered by a restart of the nodes that they have. The mempool might have been emptied by Blockchain.info and the increase in the number of transactions is due to nodes sending more transaction data to Blockchain.info after that.
In this graph https://blockchain.info/fr/charts/mempool-size?timespan=24h, we can see the mempool size falling to 0 a little bit befor 12 AM.
And since this time, mempool is slowly grows (10 MB now).
But prévious transactions (yesterday and before) are still with 0 confirmations...
What's going on ?
And since this time, mempool is slowly grows (10 MB now).
But prévious transactions (yesterday and before) are still with 0 confirmations...
What's going on ?
Jump to: