REAL Max Mempool Size in MB given core's overhead and safety buffer
Current Mempool Usage in MB and as a percentage
Mempool Transaction Count
Progress to next halving added (counts in years, days, hours, mins)
Node uptime since service was started
Current total supply of Bitcoin based on issuance schedule (may be very slightly inaccuate compared to gettxoutsetinfo but is great for monitoring at a glance without needing to wait)
I also consolidated the blockchain sync summary to one line to save screen real estate.
Here is an image of what it looks like:
Reasons 'total bitcoin supply' may not be exactly the same as gettxoutinfo:
Varied Inputs and Outputs: The total amount shown represents all unspent coins across all outputs, which includes not only block rewards but also many user transactions, each with its unique input and output values. These transactions may not align with exact multiples of the block reward.
Fee Distribution: Transaction fees also contribute to the total amount but are not typically set to neat multiples. They are instead dynamic values determined by users and miners, so they add irregular values to the total supply.
Decay in Reward Structure: If you're working within a system where block rewards decrease over time, previous block rewards might have been higher or lower than 3.125, meaning historical outputs would still affect the total.
Fractional Accumulation: With every transaction and UTXO creation, there could be small rounding effects or dust amounts, which, over thousands of transactions, contribute to a value that doesn't perfectly align with any specific multiple.
However overall this is a great at a glance metric imo to keep a check on things (with a fraction of a percent difference), especially since gettxoutsetinfo is resource and time intensive.
Properties added:
I also consolidated the blockchain sync summary to one line to save screen real estate.
Here is an image of what it looks like:
Reasons 'total bitcoin supply' may not be exactly the same as gettxoutinfo:
However overall this is a great at a glance metric imo to keep a check on things (with a fraction of a percent difference), especially since gettxoutsetinfo is resource and time intensive.