GETDown
Bitcoin block detail
Bitcoin block detail
GET
/api/explorer/block/:hashOrHeightPartial coverage. The upstream chain-data source is not reachable from our servers at the moment, so this endpoint returns 503. It stays listed so integrations do not break silently; the probe on the status page shows when it recovers.
Down. The last probe failed (HTTP 503)
Request
Query parameters
| Name | Type | Required | Default | Allowed values | Description |
|---|---|---|---|---|---|
| hashOrHeight path | string | Required | — | — | Block height or hash. Example: 840000 |
| txStart | integer | Optional | — | — | When given, includes transactions starting at this index. |
Parameters marked “path” are part of the URL.
Example request
curl -s "https://www.coinboss.com/api/explorer/block/840000"Response fields
The field table is generated from real responses, so it lists exactly what the endpoint returns. Paths use a[] for array items and {*} for objects keyed by a dynamic name such as a coin or an exchange.
| Field | Type | Unit | Description |
|---|---|---|---|
| success | boolean | — | true when the request succeeded. On failure the body is `{ success: false, code, error, request_id }`. |
| cached | boolean | — | `true` when the response came from cache. |
| data | object | — | Payload. |
| data.id | string | — | Identifier. |
| data.height | number | — | Block height. |
| data.version | number | — | Block version field. |
| data.timestamp | number | ms | Timestamp. |
| data.tx_count | number | count | Number of transactions in the block. |
| data.size | number | — | Page size. |
| data.weight | number | WU | Block weight. |
| data.merkle_root | string | — | Merkle root of the block transactions. |
| data.previousblockhash | string | — | Hash of the previous block. |
| data.mediantime | number | s | Median time of the previous 11 blocks. |
| data.nonce | number | — | Nonce of the block header. |
| data.bits | number | — | Compact encoding of the difficulty target. |
| data.difficulty | number | — | Mining difficulty of the block. |
Generated 2026-11-11 23:01 UTC from 1 real responses.
Example response
/api/explorer/block/840000 · Real response captured 2026-11-13 02:59:03 UTC.
- "success"true
- "cached"false
- "data"
- "id""0000000000000000000320283a032748cef8227873ff4872689bf23f1cda83a5"
- "height"840000
- "version"710926336
- "timestamp"1713571767
- "tx_count"3050
- "size"2325617
- "weight"3993281
- "merkle_root""031b417c3a1828ddf3d6527fc210daafcc9218e81f98257f88d4d43bd7a5894f"
- "previousblockhash""0000000000000000000172014ba58d66455762add0512355ad651207918494ab"
- "mediantime"1713570208
- "nonce"3932395645
- "bits"386089497
- "difficulty"86388558925171.02
Details
- Authentication
- None. Public endpoint.
- Rate limit
- 1200 requests per minute per IP
- Server cache
- 2m
- Edge micro-cache
- 10s
- Update frequency
- real time (300 s in-memory cache)
- Window
- single block
- Data sources
- Live Bitcoin chain data proxied at request time from public Esplora-compatible block explorer APIs.
- Exchange coverage
- Bitcoin mainnet only.
- Pagination
- Transactions are paged 25 at a time via `txStart=N`; the response returns `next_tx_start`.
- Sorting
- block order
- Units
- satoshis; bytes/weight
- Timestamps
- Unix epoch milliseconds (UTC) unless the field description says otherwise
- Response format
- json
- Stability
- Stable
Live status
DownChecked 2026-11-13 03:29:11 UTCHTTP 5032 msSchema not checked
The last probe failed (HTTP 503)
Availability, last 30 days
40.91% of 132 checks passed
Errors
Failed calls share one shape on every endpoint. The full list is on the errors page. Errors and rate limits →
| Code | HTTP | Meaning | What to do |
|---|---|---|---|
| INVALID_PARAM | 400 | A required parameter is missing or a value is not accepted. `param` names the parameter when it is known. | Do not retry unchanged; fix the request. |
| UNAUTHORIZED | 401 | The `CB-API-KEY` header was sent but the key is unknown or revoked. Public data needs no key — drop the header or use a valid key. | Do not retry unchanged. |
| FORBIDDEN | 403 | The route is not part of the public API (internal or account-only). | Do not retry. |
| NOT_FOUND | 404 | Unknown route, or the requested coin / exchange / fund does not exist. | Do not retry; check the path and identifiers against the catalog. |
| RATE_LIMITED | 429 | More requests than the per-minute limit. `Retry-After` gives the seconds to wait. | Wait for `Retry-After`, then retry with backoff. |
| INTERNAL | 500 | Unexpected server error. The message is generic by design; quote `request_id` when reporting it. | Retry once after a few seconds; report it with the request id if it persists. |
| UPSTREAM_FAILED | 503 | The data source behind this endpoint did not answer in time. No stale or substitute numbers are returned in its place. | Retry with backoff; check the status page. |
| UNAVAILABLE | 501 / 503 | The dataset is temporarily not ready (cache warming) or the endpoint has no lawful public source yet. | Retry later; the catalog marks endpoints that are unavailable by design. |
| REQUEST_FAILED | 200 | Some older endpoints answer HTTP 200 with `success: false`. Always check `success`, not only the HTTP status. | Depends on the message; treat as a failed request. |
Try it
GET
/api/explorer/block/:hashOrHeightDownParameters
string — Block height or hash.
integer — When given, includes transactions starting at this index.
Request URL
https://www.coinboss.com/api/explorer/block/840000Choose an endpoint and press “Send request”. The response, headers and timing will appear here.
More in this category
- Multi-chain address lookup /api/browser/:chain/address/:addr
- Multi-chain block lookup /api/browser/:chain/block/:hashOrHeight
- Multi-chain transaction lookup /api/browser/:chain/tx/:txid
- Detects which EVM chains an address is active on /api/browser/detect
- Balance changes among BTC rich-list addresses /api/btc/rich-flow
- BTC rich list /api/btc/rich-list
- BTC rich-list statistics /api/btc/rich-stat
- BTC rich-list holdings trend /api/btc/rich-trend
- Bitcoin address summary /api/explorer/address/:addr
- Bitcoin address transactions /api/explorer/address/:addr/txs
- Bitcoin block detail /api/explorer/block/:hashOrHeight
- Bitcoin chain tip /api/explorer/tip
- Bitcoin transaction detail /api/explorer/tx/:txid
- Count of BTC addresses holding more than a threshold /api/indicators/addr-above/:tier
- BTC on-chain valuation indicator series /api/indicators/bdc/:name
- Bitcoin reachable-node count and distribution /api/indicators/bitnodes
- BTC holder comparison series /api/indicators/btccmp/:pair
- BTC on-chain chart series /api/indicators/chain
- Exchange BTC inflow / outflow history /api/indicators/cm/exchange-flows
- BTC supply held on exchanges /api/indicators/cm/exchange-supply
- BTC non-zero address count history /api/indicators/cm/nonzero-addresses
- Government BTC holdings /api/indicators/gov-treasuries
- Bitcoin halving countdown and history /api/indicators/halving
- Share of BTC supply dormant for more than N years /api/indicators/hodl-wave-above/:years
- Bitcoin mining-pool block share /api/indicators/mempool/pools
- Strategy BTC cost basis and holdings history /api/indicators/mstr-cost
- Share of BTC supply in profit /api/indicators/supply-profit-pct
- WBTC reserve balance history /api/indicators/wbtc-balance
- Multi-chain rich list /api/rich-list/:chain
- Multi-chain rich-list balance changes /api/rich-list/:chain/flow
- Multi-chain rich-list statistics /api/rich-list/:chain/stat
- Multi-chain rich-list holdings trend /api/rich-list/:chain/trend
- Public-company / institutional coin treasuries /api/treasuries/:coin