Skip to content
Doefin

Bitcoin network data

Bitcoin mining data, explained.

Find current difficulty, estimated network hashrate, historical adjustments and examples of forecast error.

Start with the current readings. Each panel gives its source and time. The historical dataset and synthetic examples follow below.

Next difficulty adjustment estimate

Current API estimate

Bitcoin mining difficulty · source block 976,581

Current difficulty

~134.82T

T means trillion. Difficulty has no unit.

Estimated next difficulty

~148.16T

A single estimate, shown in trillions.

Estimated difficulty change
~+9.89%
Next adjustment block
977,760
Blocks until adjustment
1,179
Average block time this epoch
546 seconds
Estimated adjustment time
Forecast range
UnavailableThe API supplies a single estimate, with no lower or upper forecast limit.
Show exact source values

Analytics API, source block 976,581. Response received 19 Nov 2026, 12:08:07 UTC.

Current difficulty (no unit)
134823837323272.66
Estimated next difficulty (no unit)
148158062992607.3
Estimated difficulty change (source ratio)
0.09890109890109888
Estimated difficulty change (ratio × 100)
9.890109890109889%

Values marked ~ are rounded. Exact source values are available above.

The API does not say when its current block was recorded, so this page cannot verify the data’s age. Response received 19 Nov 2026, 12:08:07 UTC.

Last adjustment timestamp: 14 Nov 2026, 05:02:50 UTC

Read the difficulty guide

Network hashrate over recent blocks

API record

Source block 976,581 · timestamp

Source record is 8.6 minutes old (site freshness threshold: 30 minutes).

120 blocks (~20 hours)
~1,061.67 EH/s
144 blocks (~1 day)
~1,032.51 EH/s
2,016 blocks (~2 weeks)
~971.57 EH/s
Show exact source values

Hashrate API, source block 976,581 at 19 Nov 2026, 11:59:32 UTC.

120 blocks (~20 hours)
1061674789429674544226.612275 H/sExact conversion: 1061.674789429674544226612275 EH/s.
144 blocks (~1 day)
1032506339419935045975.869242 H/sExact conversion: 1032.506339419935045975869242 EH/s.
2,016 blocks (~2 weeks)
971570557510661241833.0239846 H/sExact conversion: 971.5705575106612418330239846 EH/s.

The API supplies decimal H/s values as text. Conversion to EH/s preserves their full precision.

EH/s means exahashes per second. Values marked ~ are rounded. These estimates average network work over recent blocks. They are not machine counts or forecast ranges.

Observed network research · v1.0.0

25 recorded difficulty adjustments.

From 2025-11-12 to 2026-10-16, the dataset records 11 increases and 14 decreases. Mean absolute difficulty change: 3.75%. These are historical network changes, not forecast errors.

Source: mempool.space, captured 2026-10-22. This is a fixed one-year snapshot, not a live feed. No independent check against a Bitcoin node is documented.

Forecast archive: no published predictions

The archive contains no captured provider predictions or independent timestamps proving publication before an outcome or market listing. Dated forecast examples elsewhere on this site use made-up values.

Inspect the archive status →

Synthetic forecast records

Read the dated example rows.

These rows show how a forecast, its date and an outcome fit together. The current API has no published history linking earlier forecasts to their ranges and outcomes.

Published forecast records available from the current API: 0.

Show 3 synthetic example rows (not published records)

Changes in % · dates belong to the examples

Three made-up difficulty records with example dates, forecast changes and outcomes. They are not measured history.
Target blockForecast dateForecastOutcomeOutcome date
Block 913,248Forecast dateForecast+2.31%OutcomeNot includedOutcome dateNot included
Block 911,232Forecast dateForecast+1.12%Outcome+1.84%Outcome date
Block 909,216Forecast dateForecast-0.74%Outcome-2.06%Outcome date

“Not included” means the teaching example has no outcome. It does not describe a pending live adjustment. These rows have no page of their own.

Read accuracy with care

A smaller error is not enough on its own.

An average error depends on its units, the number of forecasts and the dates tested. It cannot tell you on its own which forecast to trust.

Read the accuracy metrics

How is forecast error calculated?

The research guide explains how to compare forecasts and repeat the error calculations using a downloadable sample.

Go to ResearchRead about inputs and methods