Avg Block Interval
Estimated average time between blocks in seconds, derived from hash rate and difficulty. Target is 600s (10 min). Deviations reveal hash rate imbalances vs difficulty.
What is it?
The Average Block Interval estimates the daily average time between consecutive blocks, calculated as difficulty × 2³² / hash_rate (in seconds). Bitcoin's protocol adjusts difficulty every 2,016 blocks to keep this interval near 600 seconds (10 minutes). When hash rate grows faster than the next difficulty adjustment, intervals shorten; when miners disconnect, they lengthen. This metric directly captures the dynamic relationship between deployed hash power and protocol difficulty.
How to read
The 600-second line is the protocol target. Values below 600 indicate excess hash rate (blocks found faster than expected - typically between difficulty adjustments when new hardware comes online). Values above 600 mark a hash rate deficit. Difficulty adjustment periods (~2 weeks) create natural oscillations around the target.
Key zones
Daily average intervals above 700 seconds are rare and indicate significant network stress. During the 2021 Chinese mining ban, average intervals temporarily reached ~1200 seconds (20 minutes) before adjustment. Intervals below 500 seconds indicate a rapid hash rate influx.
What to observe
Spikes above 600 seconds persisting for several days indicate structural hash rate loss. Rapid convergence phases back to 600 after a spike show the resilience of difficulty adjustment. Interval volatility (intra-day standard deviation) is as informative as the average.
Historical context
The most abnormal average intervals were observed during the Chinese mining ban (June 2021), when ~50% of hash rate disappeared - intervals temporarily doubled. Each halving produces a temporary widening (6-8 weeks) as marginal miners are eliminated. Introduction of more efficient ASICs creates compressions (short intervals) before adjustment.
Expert notes
The interval calculated here is a daily estimate based on difficulty × 2³² / hash_rate. Hash rate itself being a statistical estimate (±10-15%), the interval has proportional uncertainty. For maximum accuracy, direct block timestamp measurement is preferable but requires access to individual block data. Our estimate is sufficient for trend analysis and stress detection.
Common mistakes to avoid
This interval is an estimated daily average, not the actual distribution of individual intervals. Individual blocks follow a Poisson distribution with high variance - some are mined in seconds, others in 60+ minutes. The average interval aggregates this variance into a single daily figure, losing information about the distribution shape.
Programmatic access
REST API
curl -sS \
'https://api.trinityinsights.io/api/v1/onchain/block-interval-distribution/history?days=90' \
-H 'X-API-Key: $TRINITY_API_KEY'MCP server
{
"tool": "get_chart_value",
"metric_id": "block-interval-distribution",
"timeframe": "1y"
}Required tier: pro. See the pricing grid for the tier list and the MCP documentation for multi-client configuration.
Related metrics
Institutional disclaimer
Trinity Insights is an educational and analytical tool. The metric above does not constitute investment advice. Trinity Insights is not a Crypto-Asset Service Provider (CASP) registered under MiCA Regulation (EU) 2023/1114. See the full disclaimer.