Landing page
Definitions of the variables that live on the landing page of the Rated Network Explorer.
The default view of the Rated Network Explorer is the "Pools" view. This represents the allocation of stake accross the highest order of aggregation of stake. All the content in this page translates equally to the "Pools", "Node Operators", and "Deposit Addresses" views of the Explorer.
Pools view of the Rated Network Explorer.
For more information on how we segregate between different entities that operate on the Beacon Chain, please refer to the Classes of aggregation section in the documentation.
At the top of the Pools view page sit four counters that show the aggregate performance of the network on the previous completed day. These are normally helpful in quickly referencing how a pool is performing compared to the network average.
The counters at the top of the Entity views landing pages.
For a deeper dive into what each of these metrics represents, please visit the Effectiveness breakdown 🔖 page in the documentation.
This is the percentage distribution of stake that maps under any given pool. We calculate this as:
Network penetration == active stake in pool / active stake on the Ethereum Beacon Chain
Where "active stake" means, the sum of 32 ETH increment balances that map to any given pool.
In order for a validator to become "active" on the network, it needs to (i) be funded with a balance of 32 ETH, and to (ii) get past the activation queue stage. Any balance that any single validator earns above 32 ETH does not count towards active stake.
This is the percentage distribution of consensus clients an operator or entity is running accross the body of validator indices that it operates.
In order to produce client distribution statistics for validator keys and accross entities, we are using blockprint, an open source client classifier. Please note that the results that blockprint produces have a relatively wide statistical confidence interval.
Since The Merge, validators have the ability to outsource block production to specialized entities called "Builders", and effectively "shop" for pre-packaged blocks through an interface agent called the "Relay". The Block Space Distribution column on the Explorer displays the distribution of blocks as it relates to the origin of those blocks. The explorer currently segregates between the different Relays blocks were procured from, as well as blocks that were built locally (showing in the distribution bars as "vanilla blocks").
Please refer to the Backward looking APR%section of the documentation for a deep dive into how we compute this metric.
The Rated model of validator performance. The colour coding in each of those values hints to the relative performance of the entity.
For more information on how this is computed and the methodology behind it, please refer to the Effectiveness rating page. You can also learn more about how we rank for relative performance via Rating percentiles.
Last modified 1mo ago