Query the chain · Network stats

Bitcoin network stats API for hashrate, difficulty and block metrics

The health of the Bitcoin network shows up in a handful of numbers: the estimated hashrate securing it, the mining difficulty that resets every 2,016 blocks, how long blocks are actually taking, block size and weight, transactions per block, and the fees paid to confirm them. The Bitcoin network stats API computes all of these from every block on the fully-indexed chain, so you can read the current state or rebuild the full history without running Bitcoin Core or scraping a chart site.

Each block header already carries its difficulty and timestamp, so hashrate estimates, difficulty over time and real block intervals fall straight out of the index, alongside per-block size, fee totals and transaction counts. Pull a single current figure over REST for a status page, or run SQL to chart difficulty across every adjustment epoch, measure how block times drifted around a halving, or correlate fees with mempool pressure. This is informational on-chain data and analytics, not financial or investment advice.

or try it below ↓

REST API · SQL · dashboards · indexed from genesis

Query Console

BTC address or sample query

btc

try:

Hit Run to query the fully-indexed Bitcoin blockchain.

BTC

30-day trend

informational on-chain data · not financial advice

REST API · SQL · dashboards, one indexed dataset. Querying the indexed Bitcoin blockchain ...

REST API SQL DASHBOARDS WEBHOOKS CSV EXPORT

Indexed from genesis queryable in seconds

On-chain data not financial advice

Why it works

What you get with network stats

Hashrate and difficulty

Read the estimated network hashrate and the mining difficulty that adjusts every 2,016 blocks, both derived from block headers and timestamps on the indexed chain, and rebuild the full difficulty and hashrate history across every adjustment epoch in SQL.

Real block metrics

Go past the 10-minute target to how blocks actually behaved: real block intervals, block size and weight, transactions per block and total fees paid, all computed per block so you can chart how the network moved over any window.

Current or full history

Pull one current figure over REST for a status page or widget, or query the entire history in SQL to study how hashrate, difficulty, block times and fees shifted around halvings and demand spikes, without running a node yourself.

What it handles

The indexed Bitcoin chain, queryable your way

Look up an address, a transaction, a UTXO, the rich list or an on-chain metric, by REST API, SQL or dashboard. The same authoritative data, reconciled block-by-block against the canonical chain, without running a node.

Read estimated hashrate and current difficulty
Rebuild difficulty history across every adjustment epoch
Measure real block intervals versus the 10-minute target
Track block size, weight and transactions per block
Chart total fees paid per block over any window

GET /v1/address/{addr} query result

200 · JSON

{
  "address": "bc1qxy2k…l0wdv8",
  "balance_btc": 68432.10,
  "balance_usd": 4612165420,
  "tx_count": 1284,
  "unspent_outputs": 37,
  "first_seen": "2014-02-09"
}

indexed from genesis · to the satoshi ✓ reconciled block-by-block

Why BitcoinDatabase

One platform, queryable three ways

Not a raw node to sync, not an indexer to build, and not five vendors to stitch together. The fully-indexed Bitcoin blockchain, available as a REST API, as SQL, and as dashboards, on one authoritative dataset.

REST API

Typed JSON for addresses, transactions, balances, UTXOs and metrics. Drop it into apps, wallets, explorers and agents with curl, Python or our SDKs.

SQL access

Run SQL directly against the indexed Bitcoin dataset for ad-hoc analysis, cohorts and exports, the same data the API and dashboards read from.

Compliance-first

Informational on-chain data and analytics only. Entity labels and flow tracing are framed as tooling to support a regulated team's own review, not accusations.

Good questions

Questions about network stats

It returns network-level metrics computed from every indexed block: estimated hashrate, mining difficulty, real block intervals, block size and weight, transactions per block and total fees paid. You can read the current value over REST or rebuild the full historical series in SQL, without running Bitcoin Core.

Hashrate is an estimate, not a directly measured number. It is inferred from the mining difficulty and how quickly recent blocks were found: if blocks arrive faster than the 10-minute target at a given difficulty, more hashing is implied. Because BitcoinDatabase holds every block header and timestamp, it computes this estimate and its full history for you as informational data.

Read every Bitcoin API question

Explore more

See every use case See pricing Back to the Bitcoin API

Stop running a node. Just query Bitcoin.

Run your first query now and get on-chain data back by REST API, SQL or dashboard, indexed from the genesis block. Informational on-chain data only, not financial advice.

See pricing

Indexed from genesis · REST · SQL · dashboards · addresses, transactions, UTXOs, metrics