Monero network status

The live panels need JavaScript, because your browser reads the numbers from the public sources itself rather than asking us for them. Everything below - what Monero makes observable, why there is no box here for your view key, and where the network version stands - works without it.

Data: your browser talks directly to xmrchain.net, Blockchair and p2pool.observer. Your browser reads these figures directly from xmrchain.net, Blockchair, p2pool.observer and a small set of public Monero nodes, so each of those operators sees your IP address while the page is open. There is nothing to type here - no address, no transaction ID, no key - so what you read never reaches us.

Explorers print the numbers and leave you to do the arithmetic. Read by your browser, from sources named on the page, with nothing to type.

A table of numbers is not an answer

This page does it: how much of a block the current backlog would fill, what each of the four fee tiers costs to send a typical transaction right now, how far apart the last twenty-five blocks actually landed, and whether the sources agree about any of it. Every Monero explorer shows the same figures: height, difficulty, hashrate, a mempool count. None of them tell you the thing you came for, which is whether to send now or wait twenty minutes. This page does the arithmetic instead of printing it. The backlog is weighed against one block’s worth of space, the four fee tiers are priced for a transaction the size you would actually send, and the two together produce one sentence. When either half is missing, it says so rather than guessing from the half it still has.

Read twice, from sources that do not share a node

Chain figures here come from two block explorers and one independent node, and the page shows you when they disagree rather than quietly picking a winner. That is not decoration. Building it turned up a widely used explorer reporting the Monero mempool a thousand times larger than it is, and a hashrate labelled "24-hour" that is really this minute’s difficulty divided by the block target.

  • Heights are compared with a two-block tolerance, because sources legitimately lag each other.
  • Difficulty is only compared between sources describing the same block: one of them reports the mined tip, the others the block being mined, and treating those as one number would show a permanent disagreement about a value the network agrees on exactly.
  • Hashrate is deliberately not compared at all. Both explorers derive it from difficulty by the same division, so agreement there is arithmetic rather than corroboration.

There is no box here for your view key

A Monero payment can be proved to someone else, and the usual way sites offer that is a form which takes your private view key, or a transaction secret key, and sends it to a server inside a web address. That drops a key covering your whole transaction history into a stranger’s access logs, into the referrer sent to whatever you click next, and into your own browser history. We do not build that form and we are not going to. The check belongs in your wallet, where the key never moves: the command-line wallet has check_tx_key, and the desktop wallet has the same thing under Advanced.

What Monero lets anyone see, and what it does not

An explorer can tell you that a transaction exists, when it was mined, how big it was, what fee it paid and how many decoys it used. It cannot tell you how much was sent, who sent it, or who received it - and neither can we. There is no address page here, because a Monero address never appears on the chain at all.

  • Visible: transaction size, fee, ring size, the block it landed in, and how many blocks have followed it.
  • Hidden by design: amounts, which sit behind commitments; the real sender, one of sixteen ring members; the recipient, who appears only as a one-time key.
  • Impossible: looking up an address to see a balance or a history. Only the holder of the view key can scan for their own payments, which is why that check belongs in your wallet.

Where the network version stands

The chain has been on consensus version 16 since August 2022. FCMP++, the next major change, is in development and audit, and no activation date or block height has been announced. Search results are full of confident quarters and block numbers for it; none of them come from the people writing it. This page will keep saying "not announced" until there is something real to say.

Questions

My transfer has not confirmed and it has been ten minutes. Is something wrong?
Almost certainly not. Two minutes is an average, not a schedule: blocks arrive at random intervals, and a live sample of recent blocks routinely holds gaps of two seconds next to gaps of seven minutes. The block rhythm panel shows that real spread instead of the target.
Can I look up a Monero address here?
No, and neither can anyone else. Monero addresses never touch the chain; what lands there is a one-time key derived for that payment alone. Any site offering you a Monero address balance is either guessing or about to ask you for a key.
When is the next Monero hard fork?
No date has been announced. The chain has run consensus version 16 since August 2022 and the next upgrade is still being built and audited. We would rather print "not announced" than repeat a quarter somebody invented for traffic.
Why does your mempool size differ from another site?
Two reasons, and one of them is a real defect. Nodes genuinely hold slightly different pools, so small differences are ordinary. Large ones usually are not: the field most sites read is named kilobytes and actually contains bytes, so trusting the label overstates the mempool by a factor of a thousand. We check that figure against the pool listing itself and say plainly when the two do not match.