Network health

Consensus facts

Proof of work

RandomX, an algorithm written by Monero contributors, used since release 0.15. [1]

Block time

2 minutes: the difficulty target is 120 seconds (DIFFICULTY_TARGET_V2), which the nodes read also report. [1]

Supply

No fixed cap. Since the end of May 2022 a tail emission adds 0.6 XMR per block, or less (FINAL_SUBSIDY_PER_MINUTE, 0.3 XMR a minute). [1] [2]

Privacy

Private by default: each input is signed among a ring of 16 outputs, stealth addresses give every payment a one-time address, and RingCT hides amounts (since block 1,220,516 in January 2017). [1] [2] [3]

Consensus facts

Proof of work

Equihash with n = 200 and k = 9. [1]

Block time

75 seconds since the Blossom upgrade (POST_BLOSSOM_POW_TARGET_SPACING), half the 150 seconds before it. [1] [2]

Supply

Capped at 21 million ZEC (MAX_MONEY). The block subsidy halves every 840,000 blocks at the pre-Blossom spacing, about four years, a period ZIP 208 keeps in time. [1] [2] [3]

Privacy

Optional: transparent transactions are public, and shielded pools (Sprout, Sapling, Orchard and, since NU6.3 at height 3,428,143, Ironwood) use zero-knowledge proofs. Since NU6.3 no new value may enter the Orchard pool. [1] [2]

Consensus facts

Proof of work

BLAKE3, with the ASERT difficulty algorithm, under DCP-0011. [1]

Block time

5 minutes (TargetTimePerBlock). [1] [2]

Supply

Capped just under 21 million DCR (the documentation's upper limit is 20,999,999 DCR and a fraction). The block reward falls by a factor of 100/101 every 6,144 blocks; 1% goes to the miner, 89% to the voters and 10% to the treasury (DCP-0012). [1] [2] [3]

Proof of stake

Five tickets are called to vote on each block and at least three must approve it. The pool targets 40,960 tickets (TicketPoolSize 8,192 times 5 tickets per block), and a ticket not called expires after 40,960 blocks. [1] [2]

Privacy

Optional mixing: CoinShuffle++ (CSPP) builds CoinJoin transactions from the coins of several users. [1]

Consensus facts

Proof of work

FiroPoW, a variant of ProgPoW aimed at graphics cards, since block 419,264 on 26 Oct 2021 (nPPBlockNumber, nPPSwitchTime). [1] [2]

Block time

Not confirmed: chainparams.cpp sets a 5-minute spacing (nPowTargetSpacingMTP), but the explorer listed 590 blocks for 22 Oct 2026, one every 2.4 minutes on average, and this page has not found the rule behind the difference. [1] [2]

Supply

Capped at 21 million FIRO (MAX_MONEY). [1]

Finality

Proof of work with LLMQ ChainLocks: quorums of masternodes lock blocks, which the README describes as protection against 51% attacks and quick finality. [1]

Privacy

Optional: the Spark protocol, which supports large anonymity sets without a trusted setup. [1]

Consensus facts

Consensus

Hybrid: ProgPoWZ mining and Zarcanum proof of stake secure the chain together. [1]

Block time

About 60 seconds: proof-of-work and proof-of-stake blocks each target 120 seconds, and the combined target is (120 + 120) / 4 = 60 seconds (DIFFICULTY_TOTAL_TARGET). [1]

Supply

A reward of 1 ZANO per block (CURRENCY_BLOCK_REWARD). [1]

Privacy

Private by default: stealth addresses, d/v-CLSAG ring signatures with decoys (a mandatory decoy set of 15 since hard fork 4), hidden amounts and confidential assets. [1] [2]

Consensus facts

Proof of work

Equihash with n = 200 and k = 9. [1]

Block time

60 seconds. [1]

Supply

Capped at 200 million ARRR. [1]

Security

Delayed proof of work (dPoW) from the Komodo Platform, which the README calls an additional security layer; the explorer reports the latest notarised block. [1]

Privacy

Private by default: zk-SNARKs shield all peer-to-peer transactions. [1]

Consensus facts

Proof of work

Five algorithms: scrypt, x17, Lyra2rev2, myr-groestl and blake2s. [1]

Block time

30 seconds (nPowTargetSpacing = 30). [1] [2]

Supply

The README gives a total supply of 16,521,951,238 XVG, marked complete; MAX_MONEY in the code is 16,555,000,000 XVG. [1] [2]

Reorganisations

Nodes refuse to switch to a competing branch that would undo 7 or more blocks, even a longer one. The README calls this a local safeguard, not cryptographic finality. [1]

Privacy

Network level: a node can run as a Tor hidden service and connect to other nodes through Tor. [1]

How the figures are read

The daily job reads every source once, after 01:20 UTC, and keeps one reading per series per UTC day. On the last run every source was read.

Histories come from the sources that publish them: Coin Metrics' daily series (Monero and Verge since 2014, Zcash since 2016), dcrdata's daily charts (Decred, since 2016), and the Zcash counts the Activity page already collects. Firo and Pirate Chain have no downloadable history, so their daily blocks are read from the explorers a day at a time. Everything else starts on the first daily reading.

The consensus facts are dated constants from each project's own code and documentation, checked on 23 Oct 2026. The series behind the charts are in nethealth.json, under the site's licence and credits.