A privacy network requires the use of a public machine. To check what you can inspect without touching someone else's transfer, I opened the new @BeldexCoin explorer. The user path remains protected while the operator path can now be read. On screen just now: • 3,523 active masternodes • 0 waiting to join • 23 decommissioned • 10,000 BDX to run one • 35.2M BDX staked • mempool live at 20 txs What was important wasn't the 3,523. It was the 23. On the Master Nodes page, those twenty-three are indicated as not being awarded rewards and as undergoing deregistration; most have the entry 'Last Uptime Proof: Not Received' and one line states that deregistration is about to take place. The Quorums tab serves the same purpose. Testing is not merely for show. Various nodes check other nodes to see if they are up and running. If you fail enough of these tests, the group will vote you off. The upgrade isn't a more attractive dashboard; it's a means of observing the backbone in action—by showing who is currently online, who has dropped off, the reason for their drop-off, and the fact that the pool remains active. Registration, BNS, and stake changes are visible but it is not possible to use the same page to reconstruct a private payment, a BChat route, or a BelNet session. v7.0.4 is beside this one. Flash sync and the tx pool are what the operator experiences. The explorer is the place where everyone else checks to see whether that work has been accepted. I am not considering the map as merely decorative; rather, I am using the 23 decommissioned nodes as the very first honest element on the page. If you visited explorer.beldex.io today, would you have checked the active count or would you have looked at what dropped out?