Bitcoin block explorer API for blocks, transactions and addresses

Yes. It returns blocks, transactions, inputs, outputs, script types, addresses, balances, confirmations and mempool entries, which is everything an explorer renders. We keep the chain indexed and reconciled, so you focus on the UI.

Each block is parsed and reconciled as it confirms, and unconfirmed activity is available through the mempool endpoints. The same indexed data is also queryable via SQL and dashboards.

Blockstream Esplora and mempool.space are the two most widely used free public endpoints, with BlockCypher and Blockchair close behind. All four answer address lookups without a key, and all four throttle you once traffic is real. Worth knowing before you build on one: tested first-hand, none of their address endpoints returns a timestamp, so anything date-based needs a second call.

Request the block by either identifier and you get the same record: hash, height, timestamp, transaction count, size, weight, merkle root, difficulty and the previous block hash. Height is the convenient key for walking the chain in order, hash is the stable key, because a height can briefly point at a block that a reorg later replaces.

Ask for the block transactions and page through them. Public explorers make this slow on purpose: Esplora returns 25 transactions per request, so a busy 4,000 transaction block is over 170 sequential calls and several minutes of waiting. Here the block is already indexed, so you request its transactions once or select them in SQL.

Not on your side, which is the point of using one. Behind the API a node and an indexer are still required, along with roughly 600 GB of disk, a multi-day initial sync and constant reconciliation. We carry that so your explorer calls an HTTPS endpoint instead of babysitting Bitcoin Core.

Yes. POST /v1/tx/broadcast takes a signed raw transaction as hex and returns HTTP 201 with the txid. If the network refuses it, you get HTTP 422 with the node's own reason in network_said. When we re-sent an already-confirmed transaction to three public explorer endpoints on 25 September 2026, all three answered HTTP 400, the same code they gave 80 bytes of zeros.

Look it up by txid. GET /v1/tx/{txid} returns whether it is still in the mempool or which block height confirmed it, and the broadcast response links straight to that lookup. Checking by txid is also the safe response to any broadcast error, because a rejection can mean the transaction already went through.

Here the Developer plan is $49 a month for 500,000 API credits at 10 requests per second with one year of history. Growth is $199 for 5 million credits, SQL over the indexed chain and full address history since 2009 over REST, and Scale is $799 for 50 million credits with bulk exports and webhooks. A block, transaction or address lookup costs credits from the same pool.