Grouped by the UTC date when each mint transaction landed on chain. Time moves left to right; the last point is today or the latest date with mints.
30-day total
20,730mints
sum of mints across the window
Last 7 days
2,377mints
trailing weekly count
Fig. V.B.1.Daily mint count over the past 30 days, grouped by mint transaction date.
y · mints/x · day (UTC)
Plate V.D./Burn distribution
Minted burn, by bucket.
Minted blocks grouped by burn amount. Each bar shows how many eNATs fall into that burn range.
Sample
9,774,415blocks
of 9,774,415 minted blocks
Range
0.0000 – 220.9351ETH
min – max burn observed in sample
Fig. V.D.1.Minted block count per burn bucket. The x-axis label is the bucket's upper burn bound.
y · blocks/x · ETH
Plate V.E./Holder concentration
Where the wholes currently sit.
This shows how much of the whole supply is held by the top 1, top 10, and top 100 addresses. Small samples can make a single address dominate the early distribution.
Active holders
7,417wallets
wallets holding ≥ 1 whole
Gini
0.910
highly concentrated — supply sits in a few wallets
Fig. V.E.1.Share of all wholes held by the top-1 / top-10 / top-100 holder cohorts.
Top 1 share
1.8%
Plate V.F./Indexer health
Reference indexer.
Head block
#26,330,682
Finality lag
64blocks
blocks behind head that are committed
Processing lag
0blocks
blocks the indexer is behind head (0 = caught up)
Uptime
151h 17m
continuous runtime since the last restart
Reference indexer
Sync status
n · 30 day (UTC)min · 2 mints · avg · 691 · max · 2,742
n · 12 buckets · Σ 9,774,415 blocks
Reading note — buckets are equal-width over the observed min–max range. Most blocks live in the small-burn bands; most ETH lives in the large-burn tail.
Top 10 share
11.8%
Top 100 share
49.8%
Computed across 2,478,540 wholes held by 7,417 addresses.
Counts addresses holding whole blocks, not bENAT holders or individual people.
Synced
ETH RPCReachable
indexer state filePresent
state root0xef06c51b…29e262
v1 runs as a single instance. Multi-indexer witness consensus (m/n threshold co-signing) is listed in protocol spec §10 as roadmap; the UI entry stays closed until backend support exists.
