Ethereumgarden
Real-time blobspace data · growing Ethereum
Ethereum
Abstract Ethereum garden with layered hills, luminous leaves, network lights, and a central Ethereum diamond
Live blobspace

Watch Ethereum's
Blockspace Bloom

Every canonical block adds a new petal to the garden. From mainnet to L2s, blockspace and blobspace is Ethereum’s shared bandwidth—growing the ecosystem, together.
Block—
Base fee—
Blobs—
Capacity—
FreshnessChecking…
Embedded Etherscan snapshot loaded.25 consecutive blocks through #25,559,661 at July 18, 2026 12:42:59 UTC.
RootsCanonical historyConsecutive block heights and parent hashes keep every average anchored to one chain.
LightIndependent verificationSecondary RPC, Etherscan, and transaction-level samples illuminate source disagreement.
BloomsBlobspace in useEach active petal represents one occupied blob slot in the latest Ethereum block.
SeasonsFinality over timeProvisional growth stays visible, while headline averages wait for finalized conditions.
Ethereum L1 gas

Track the chain’s block gas price.

Every point is the EIP-1559 baseFeePerGas recorded in a canonical execution-block header. Headline averages end at the finalized block; newer blocks remain provisional. Priority fees are intentionally excluded.
Finality-aware gas tracking
Finalized base fee
—
Awaiting finalized data
Provisional base fee
—
Awaiting latest head
Gas utilization
—
Finalized block gas used / limit
1 hour base fee
—
Block-weighted finalized average
24 hour base fee
—
Block-weighted finalized average
7 day base fee
—
Block-weighted finalized average
24 hour low–high
—
Complete finalized window required
OFFLINE SNAPSHOT

Ethereum L1 base fee

Canonical block-header base fee in gwei · excludes validator priority fees
Base fee1H rolling avg24H rolling avg7D rolling avg
1H selected · connect live data for gas history
Blob fee market

The economics of shared bandwidth.

Price, burn, capacity pressure, and the cost of Ethereum data availability. Values use the separate EIP-4844 blob-fee market, not the execution base fee.
24H blob fees
—
Complete finalized or consecutive window required
Average cost / blob
—
Per 128 KiB blob
Cost / MiB
—
Blob capacity basis
7D blob fees
—
ETH burned
24H blob fee range
—
Gwei per blob gas
ETH / USD
—
Optional Etherscan market feed
OFFLINE SNAPSHOT
Separate EIP-4844 market

Blob base fee

Blob gas price and rolling averages, distinct from the execution base fee
Blob base fee1H rolling avg24H rolling avgPrior period
Connect live data to load blob-fee history
Ethereum blobspace

Measure the data garden’s blooms.

Exact blobs per block, finalized rolling averages, protocol capacity, source verification, and complete 30-day history.
Latest block
—
Awaiting connection
Current blobs
—
Per latest block
1 hour average
—
Rolling blobs per block
24 hour average
—
Rolling blobs per block
7 day average
—
Rolling blobs per block
30 day blobs
—
Total data-availability units
30 day capacity
—
Versus 21-blob maximum
OFFLINE SNAPSHOT

Blobs per block

Server mode charts finalized canonical blocks; aggregated long-range points preserve minimum, maximum, and average values
Blobs/block1H rolling avg24H rolling avg7D rolling avg
1H selected · embedded snapshot loaded

Root system health

Completeness manifest for the finalized 30-day dataset and deterministic cross-source samples
Open JSON
First block—
Last block—
Block count—
Total blobs—
Missing heights—
Parent continuity—
Finality level—
Source agreement—
Dataset freshness—
Protocol schedule—
Secondary RPCNot checked
Etherscan samplesNot checked
Transaction blob hashesNot checked

Garden ledger

Newest Ethereum blocks, linked directly to Etherscan
BlockTimeBase feeBlobsUtilizationBlob gas usedFinalitySource
Ecosystem intelligence

See who is using the garden—and how it is growing.

A small, exact sample of recent canonical Ethereum blocks adds address-level blob submitters, transaction composition, RPC health, and protocol-capacity context. Labels never guess an L2 identity.
Waiting for a public RPC sample

Top blob submitters

Ranked by exact blob count in the sampled blocks

Addresses are shown instead of inferred rollup names. Fee estimates use each block’s canonical blob base fee and the transaction’s exact blob-versioned-hash count.

Loading recent blob transactions…
Source: keyless Ethereum JSON-RPC · recent-block sample · no attribution registry

Ethereum activity composition

Mutually exclusive transaction classes in the same exact sample
Contract calls
—
ETH transfers
—
Blob txs
—
Contract creates
—
Awaiting exact full-transaction blocks.

Network health

Live client response, block cadence, finality, and sampling coverage
Not observed
Chain ID—
Finality gap—
Avg block time—
Largest gap—
RPC latency—
Health values are browser-observed and describe the selected public endpoint—not the entire network.

Blob-capacity seasons

Mainnet protocol annotations—use these breakpoints when comparing utilization across eras
DencunBlob target 3 · maximum 6 · EIP-4844 launches blobspace.
Prague / PectraTarget rises to 6 · maximum to 9.
BPO1Target rises to 10 · maximum to 15.
BPO2 · currentTarget 14 · maximum 21 · base-fee update fraction 11,684,671.
Capacity annotations follow Ethereum mainnet’s published BPO schedule. The live cards continue to use the page’s active protocol configuration.

Device-local alerts

Set thresholds without creating an account or sending values to a server
Alerts are off on this device.

Checks run only while this page is open. Browser notifications are requested only after you press Save alerts; in-page notices remain available if notifications are unsupported or denied.

Daily garden note

A copy-ready summary generated from the values currently displayed
Waiting for Ethereum data…
The note carries the current data mode and sample timestamp so snapshot or partial data cannot be mistaken for live completeness.
Ethereum accounts · L1 + L2

Watch funded accounts take root.

Compare addresses holding at least 0.001 ETH, 0.01 ETH, and 0.1 ETH across Ethereum L1, Base, Arbitrum One, OP Mainnet, and Robinhood Chain. These are on-chain addresses—not unique people or wallets.
Auto-load on Metric definitions Live public archive Historical archive Snapshot provenance Distribution cross-check
Ethereum L1 renders an embedded, verified Coin Metrics archive immediately, then checks the Community API for newer exact observations. The linked DoltHub and GitHub archives remain historical provenance sources and never delay the initial chart. Coin Metrics does not publish these native-ETH balance cohorts for the four L2 networks, and their public explorer APIs do not expose an exact threshold-count aggregate. The stack therefore labels missing L2 observations as unavailable—never zero—and accepts exact dated L2 snapshots below. Metrics requested: AdrBalNtv0.001Cnt, AdrBalNtv0.01Cnt, and AdrBalNtv0.1Cnt. Coin Metrics community data is CC BY-NC 4.0; confirm that license fits the intended deployment.
Ethereum L1 ≥ 0.001 ETH
61.6M
Embedded archive snapshot
61,573,887 · Jun 18, 2025
Ethereum L1 ≥ 0.01 ETH
27.4M
Embedded archive snapshot
27,353,385 · Jun 18, 2025
Ethereum L1 ≥ 0.1 ETH
5.22M
Embedded archive snapshot
5,224,234 · Jun 18, 2025

Larger funded-account cohorts

Exact Coin Metrics Ethereum L1 address counts only—never inferred users or estimated thresholds
Checking public metrics
Accounts ≥ 1 ETH—Awaiting exact daily observations
Accounts ≥ 10 ETH—Awaiting exact daily observations
Accounts ≥ 32 ETHUnavailableCoin Metrics does not publish an exact 32 ETH address-count metric; no synthetic estimate is shown.
Public metrics: AdrBalNtv1Cnt and AdrBalNtv10Cnt. The 32 ETH validator-deposit threshold is conceptually different from an address balance and is intentionally not approximated.

Funded-account ecosystem stack

Five networks · stacked by native-ETH balance band · exact dated observations only
Count view · 1 of 5 networks has an exact cohort snapshot
Blank L2 bars mean an exact threshold snapshot is unavailable; they are not zero-address observations. Add a dated snapshot in Developer view to populate the stack.
0.001–0.01 ETH 0.01–0.1 ETH ≥ 0.1 ETH
Embedded Coin Metrics month-end snapshot · 120 observations · Jul 31, 2015 to Jun 18, 2025
Address count, not user countOne person or organization can control many addresses, and balances can belong to contracts or custodians.
Chain-specific stateThe same address may appear on several networks. Each bar counts that chain’s native-ETH state independently.
True stacked bandsCumulative thresholds are converted into non-overlapping bands: 0.001–0.01, 0.01–0.1, and at least 0.1 ETH.
Missing is not zeroOnly exact dated observations are drawn. Unpublished L2 cohorts remain visibly unavailable and are never estimated.
Add exact L2 balance snapshots

Enter cumulative address counts from one exact, dated source. All three thresholds are required for each populated network, and counts must descend as the threshold rises. Values saved here are device-local. To publish them for every visitor, copy the downloaded JSON values into EMBEDDED_L2_SNAPSHOT in this same file before uploading it.

NetworkAddresses ≥ 0.001 ETHAddresses ≥ 0.01 ETHAddresses ≥ 0.1 ETH
Base
Arbitrum One
OP Mainnet
Robinhood Chain
No L2 values are inferred.
NetworkAt least 0.001 ETHAt least 0.01 ETHAt least 0.1 ETHObservation