All metrics › Throughput & Block Production
Compute Units per Block
Latest value: 17.8 million CU on 3 November 2026.
30-day average: 21.6 million CU, down 24.9% from a year earlier (28.7 million CU).
Highest daily value since January 2025: 51 million CU on 30 January 2026.
The default network series of the Explorer (total_cu_avg). Download the data (CSV)
Compute units (CUs) consumed per block. CUs measure program execution cost in the Solana runtime, where each CU roughly corresponds to one BPF instruction. Each block has a compute limit: 48M CU until April 2025, then 50M, 60M (July 2025) and 100M (July 2026, SIMD-0286). From August 2026 the limit falls with each slot-time step (SIMD-0525) to 87.5M, 75M, 62.5M and 50M at 200 ms, so compute per second stays near 250M CU and per-block values fall when slots get shorter. Higher values mean denser, more computation-heavy blocks. Vote and Non-vote split each block by transaction type, and Successful and Failed by transaction outcome; the % view shows the share of the type's compute units. These views come from Dune block data.
Open the chart in the Explorer
- Area
- Throughput & Block Production
- Frequency
- Daily
- Unit
- Compute units
- Split by
- Network, Client, Scheduler, Validator
- Source
- Firedancer
Monthly averages
| Month | Compute Units per Block |
|---|---|
| November 2026 (to 3 November) | 15.8 million CU |
| October 2026 | 23.1 million CU |
| September 2026 | 32.8 million CU |
| August 2026 | 40.9 million CU |
| July 2026 | 34.4 million CU |
| June 2026 | 33.9 million CU |
| May 2026 | 32.5 million CU |
| April 2026 | 35.2 million CU |
| March 2026 | 40 million CU |
| February 2026 | 42.1 million CU |
| January 2026 | 35.9 million CU |
| December 2025 | 26.5 million CU |
What it shows
Compute units (CUs) consumed per block. One CU corresponds roughly to one BPF instruction. Each block is capped at up to 100M CUs at 400 ms slots (raised from 48M to 50M in April 2025, to 60M in July 2025, and to 100M on 2026-07-29 via SIMD-0286 at epoch 1009, slot 435,888,000). SIMD-0525 then cuts the cap with each slot-time step: 87.5M at 350 ms, 75M at 300 ms, 62.5M at 250 ms and 50M at 200 ms. Higher average CU usage indicates blocks are fuller; sustained near-cap usage suggests network congestion.
How it is computed
Firedancer reports average compute units per block for each validator each day, along with 10th, 50th, and 90th percentile values across that validator's blocks. Network, client, and scheduler figures are a blocks-produced weighted average across all validators in the group. A 7-day rolling average is available at the network level.
Aggregation: Blocks-produced weighted average. Validators that produced more blocks contribute proportionally more.
Things to know
- The block compute cap changed over time: 48 million CUs before April 2025, 50 million from April 2025, and 60 million from July 2025. Comparisons across these dates should account for the changing ceiling.
- In the Total view, network-level percentiles (10th, 50th, 90th) are block-weighted averages of per-validator percentiles, not a true network-wide block distribution. The Vote, Non-vote, Successful and Failed views come from the cost units of each block in Dune, and their percentiles are true percentiles of the blocks. The % view is the share of the selected type's compute units, for example the failed share of non-vote compute.
- The Vote, Non-vote, Successful, Failed and % views start on 14 August 2025. Dune has cost units from 12 August 2025, and on the first two days 2 to 5 percent of the blocks have none.
- Higher average compute units indicate fuller blocks; sustained usage near the cap may signal congestion.
Full method and formula in the Methodology