BitcoinDatabase.com

On-chain metrics · On-chain metrics

On-chain metrics for Bitcoin, with the raw data underneath

On-chain metrics turn the raw ledger into signal: daily active addresses, realized capitalization, SOPR, HODL waves, supply by age, and exchange inflows and outflows. BitcoinDatabase computes these from on-chain data, so every metric ties back to the exact addresses and transactions that produced it.

or try it below ↓

REST API · SQL · dashboards · address history from genesis

Query Console
btc
try:

Hit Run to query the Bitcoin blockchain.

Live from the chain for .

BTC

Balance trail

informational on-chain data · not financial advice

REST API · SQL · dashboards, one indexed dataset. Reading the chain ...

Pull a metric time series over the API, write SQL to build your own custom indicator, or watch them on a dashboard, then drill straight down to the underlying on-chain data. Metrics are informational analytics about network activity, not financial, investment or trading advice.

REST API SQL DASHBOARDS WEBHOOKS CSV EXPORT

History from genesis queryable in seconds

On-chain data not financial advice

Why it works

What you get with On-chain metrics

The metrics that matter

Active addresses, realized cap, SOPR, HODL waves, supply by age and exchange flows are computed daily from the fully-indexed chain.

Drill to the raw data

Every metric ties back to the exact addresses and transactions behind it, so you can audit a number instead of trusting a black box.

Build your own

Query standard metrics over the API or write SQL against the raw ledger to define custom indicators on your own terms.

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.

  • Track daily active addresses and supply by age
  • Read realized cap and SOPR series
  • Pull daily on-chain transaction volume and counts over REST
  • Monitor exchange inflows and outflows
  • Build custom metrics in SQL
  • Drill from any metric to the raw chain data
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 any HTTP client.

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 On-chain metrics

Standard metrics include active addresses, transaction counts and on-chain transaction volume, realized cap, SOPR, HODL waves, supply by age band and exchange inflows and outflows, all computed from the indexed chain. You can also build custom indicators in SQL against the raw data.
Call the metrics endpoint with a date range and it returns a daily series: total value transferred on-chain, transaction count, and the adjusted volume that strips change outputs. Because the series is computed from the indexed chain rather than reported by an exchange, you can drill from any day straight to the transactions behind the number.
On-chain transaction volume is the value actually moved between addresses in blocks, settled by the Bitcoin network itself. Trading volume is buying and selling reported by exchanges, most of which never touches the chain because it nets out inside their own books. The two measure different things and routinely diverge.
Raw volume counts every output, including change returned to the sender, so a wallet moving one coin can register far more than one coin of volume. Adjusted volume estimates and removes those self-transfers so the figure reflects value that genuinely changed hands. Both are available, and it is worth stating which one a chart uses.
More than most people expect, and it varies wildly with the window. We measured all 6,054 transactions in block 962,547 on 15 August 2026: raw output volume was 3,225.69 BTC, but only 189.37 BTC reached an address that was not already an input, so 94 percent was change. Over multi-year windows published estimates settle nearer three to four times rather than seventeen.
Yes, and this is the main reason short-window volume charts mislead. In block 962,547 a single Taproot address swept dust back into its own stack and sent 2,460.46 BTC to itself, which was 76 percent of the whole block's raw volume. The value that changed hands in that transaction was about 140 dollars of dust plus a 596 satoshi fee.
No. They are informational analytics about network activity. BitcoinDatabase provides data and metrics only, not financial, investment or trading advice, and any decision you make is your own.
GET /v1/metrics/{metric} returns seven daily series: active-addresses, realized-cap, sopr, exchange-flows, hashrate, difficulty and block-fees. Each call costs 10 credits. The list is the same on every plan; the plan only decides how far back the series reaches, one year on Developer. An unknown name returns a 404 that lists every available series.
Read the covers field. Every response states the first and last day that actually have a point, plus point_count and the history window your plan allows, so a gap at the end reads as a gap instead of a flat line. The response also carries the unit and a one-line definition of the metric, so a chart never has to guess what it is plotting.
Net bitcoin flow to exchanges for the day in US dollars: inflow minus outflow, with both components returned on each point. Keep both, not just the net. On 28 September 2026 one exchange hot wallet took in 2,191.47 BTC of customer deposits in 33 blocks while the cold addresses it feeds did not move by a single satoshi.

Explore more

More ways to query Bitcoin with BitcoinDatabase

Stop running a node. Just query Bitcoin.

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

See pricing

History from genesis over REST · SQL · dashboards · addresses, transactions, UTXOs, metrics