> ## Documentation Index
> Fetch the complete documentation index at: https://docs.bloklake.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Chain status

> GET /status: the range of blocks served and the finalized block.

```http theme={null}
GET https://api.bloklake.com/v1/chains/{chain}/status
```

No key needed, not billed.

## Example

```bash theme={null}
curl https://api.bloklake.com/v1/chains/eth/status
```

```json theme={null}
{
  "chain_id": 1,
  "first_block": 0,
  "archive_height": 21034551,
  "finalized_block": 21034480
}
```

## Response

**chain\_id** `integer`

The chain's id.

**first\_block** `integer | null`

The lowest block you can query.

**archive\_height** `integer | null`

The newest block you can query: the chain head as Bloklake sees it.

**finalized\_block** `integer | null`

The newest block that can no longer change. Blocks above it, up to `archive_height`, can still be replaced by a reorg.

All three block numbers are `null` only if the chain has no data yet.

## Uses

* Decide the range of a backfill: from `first_block` (or later) to `archive_height`, or to
  `finalized_block` if you only want final data.
* Monitoring: how far the chain's data is from the real chain head.

Every query response carries `archive_height` and `finalized_block` too, so a running client
rarely needs this endpoint.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.