Skip to main content
added 27 characters in body
Source Link
Murch
  • 77.8k
  • 35
  • 190
  • 641

You're not missing anything. If the two where sourced from the same full node, they should show the same data. It appears that there are two distinct sources used for the graphgraphs.

Sharp decline in mempool chart with slow recovery

By the way, the mempool chart of today indicates that the full node sourcing the mempool count chart was uncleanly shut down today, which is not reflected in the other unconfirmed transaction count either. On a clean restart, it wouldthe node should have simply reloaded the persisted mempool state, but instead the graph indicates that it took hours to build up transactions in the mempool. (Alternatively that full node predates Bitcoin Core 0.14.0 when the feature was introduced.)

You're not missing anything. If the two where sourced from the same full node, they should show the same data. It appears that there are two distinct sources used for the graph.

Sharp decline in mempool chart with slow recovery

By the way, the mempool chart of today indicates that the full node sourcing the mempool count chart was uncleanly shut down today, which is not reflected in the other count either. On a clean restart, it would have simply reloaded the persisted mempool state, but instead it took hours to build up transactions in the mempool. (Alternatively that full node predates Bitcoin Core 0.14.0 when the feature was introduced.)

You're not missing anything. If the two where sourced from the same full node, they should show the same data. It appears that there are two distinct sources used for the graphs.

Sharp decline in mempool chart with slow recovery

By the way, the mempool chart indicates that the full node sourcing the chart was uncleanly shut down today, which is not reflected in the other unconfirmed transaction count. On a clean restart, the node should have simply reloaded the persisted mempool state, but instead the graph indicates that it took hours to build up transactions in the mempool. (Alternatively that full node predates Bitcoin Core 0.14.0 when the feature was introduced.)

Source Link
Murch
  • 77.8k
  • 35
  • 190
  • 641

You're not missing anything. If the two where sourced from the same full node, they should show the same data. It appears that there are two distinct sources used for the graph.

Sharp decline in mempool chart with slow recovery

By the way, the mempool chart of today indicates that the full node sourcing the mempool count chart was uncleanly shut down today, which is not reflected in the other count either. On a clean restart, it would have simply reloaded the persisted mempool state, but instead it took hours to build up transactions in the mempool. (Alternatively that full node predates Bitcoin Core 0.14.0 when the feature was introduced.)