Bitcoin blockchain API for the entire indexed chain

Blocks, transactions, inputs, outputs, addresses, balances, UTXOs, script types, entity labels and flows, reconciled block by block. Address and transaction history reaches back to the 2009 genesis block over REST, and SQL and dashboards run over the indexed chain, which grows with every new block.

Yes. New blocks are parsed and reconciled as they confirm, and unconfirmed activity is visible in the mempool. It provides informational on-chain data and is not financial or investment advice.

Not for reading data. A node is required if you are validating consensus yourself or broadcasting your own transactions. For queries against history, an indexed API answers in milliseconds what a fresh node needs days to sync and around 390 to 430 dollars a month to host on AWS once you add the storage a full index requires.

Five: blocks with height, hash, time and transaction count; transactions with txid, block height, fee, size and weight; outputs with txid, vout, address, value, script type and spent flag; inputs linking a spending transaction back to the output it consumed; and a daily metrics table. Inputs join to outputs on the previous txid and vout pair.

You do not connect in the usual sense. There is no PostgreSQL wire protocol, no host, port or password, and psql and DBeaver will not attach to it. SQL is a POST to the query endpoint with your API key as a bearer token, and the result comes back as JSON. It is available from the Growth plan upward and costs more credits than a plain REST lookup.

Over REST, to block 0, mined in January 2009: address and transaction history comes back in full. SQL and dashboards run over the indexed chain, which grows with every new block. One quirk worth knowing: the genesis block coinbase is not in the UTXO set, because Bitcoin Core never adds it, which is why providers can report the genesis address balance 50 BTC apart and both be right.

Usually because they answer slightly different questions. Checked on 30 August 2026, Blockstream and mempool.space both report the genesis address at 5,743,007,305 satoshis while BlockCypher reports 10,744,099,575. The roughly 50 BTC gap is the unspendable genesis coinbase. Neither number is wrong, they use different conventions about what counts as a balance.

Tight enough to shape your architecture. BlockCypher documents roughly 3 requests per second and 100 per hour on its free tier, with limits resetting on the UTC hour. Blockchair answered a two-address request with HTTP 430 and an IP blacklist notice on 30 August 2026. Any workload that loops over thousands of addresses needs a paid, indexed backend.

Yes, every output row carries its script type, which matters more than it sounds. In block 963,670 native SegWit P2WPKH accounted for 56.91 percent of outputs, OP_RETURN 18.90 percent and Taproot 12.54 percent. Notably, no public address endpoint we tested returns a script type at all; it is only exposed per transaction output.