2026-07-24
across 90 days
2026-05-19, 1.017s a block
2026-06-24, 1.280s a block
Block production
Blocks produced each day, counted between UTC day boundaries.
Last 30 days
| Day | Blocks | Block time | First block |
|---|---|---|---|
| 2026-07-24 | 76,852 | 1.124s | 91,076,594 |
| 2026-07-23 | 79,903 | 1.081s | 90,996,691 |
| 2026-07-22 | 81,882 | 1.055s | 90,914,809 |
| 2026-07-21 | 84,430 | 1.023s | 90,830,379 |
| 2026-07-20 | 84,352 | 1.024s | 90,746,027 |
| 2026-07-19 | 83,774 | 1.031s | 90,662,253 |
| 2026-07-18 | 83,116 | 1.040s | 90,579,137 |
| 2026-07-17 | 83,234 | 1.038s | 90,495,903 |
| 2026-07-16 | 83,687 | 1.032s | 90,412,216 |
| 2026-07-15 | 83,130 | 1.039s | 90,329,086 |
| 2026-07-14 | 84,019 | 1.028s | 90,245,067 |
| 2026-07-13 | 83,011 | 1.041s | 90,162,056 |
| 2026-07-12 | 83,018 | 1.041s | 90,079,038 |
| 2026-07-11 | 81,193 | 1.064s | 89,997,845 |
| 2026-07-10 | 80,323 | 1.076s | 89,917,522 |
| 2026-07-09 | 83,584 | 1.034s | 89,833,938 |
| 2026-07-08 | 83,339 | 1.037s | 89,750,599 |
| 2026-07-07 | 84,466 | 1.023s | 89,666,133 |
| 2026-07-06 | 82,124 | 1.052s | 89,584,009 |
| 2026-07-05 | 83,308 | 1.037s | 89,500,701 |
| 2026-07-04 | 81,829 | 1.056s | 89,418,872 |
| 2026-07-03 | 84,451 | 1.023s | 89,334,421 |
| 2026-07-02 | 84,761 | 1.019s | 89,249,660 |
| 2026-07-01 | 82,929 | 1.042s | 89,166,731 |
| 2026-06-30 | 74,343 | 1.162s | 89,092,388 |
| 2026-06-29 | 68,731 | 1.257s | 89,023,657 |
| 2026-06-28 | 69,446 | 1.244s | 88,954,211 |
| 2026-06-27 | 69,571 | 1.242s | 88,884,640 |
| 2026-06-26 | 69,550 | 1.242s | 88,815,090 |
| 2026-06-25 | 69,024 | 1.252s | 88,746,066 |
Go deeper
A UTC day boundary maps to exactly one block number, so blocks per day is the difference between two boundaries rather than an estimate, and average block time is the day divided by that count. Boundaries are looked up from an index for speed, then a sample of them is re-derived by bisecting the chain itself, and both numbers are printed above.
An earlier version of this page interpolated the boundaries from the RPC directly to avoid the lookup. It landed twenty to a hundred blocks off and was thrown out. Data is cached for six hours. SOCI4L is the reputation layer for Avalanche, and these are the same public sources behind our wallet reputation profiles.