---
title: "POST /block/latest"
method: POST
path: "/block/latest"
---

# POST /block/latest

`POST /block/latest`

Get the latest block. Useful for checking synchronization process and pagination

## Request body

- BlockLatestRequest
  - `offset` number, double, required — Note: an offset of -1 is treated the same as an offset of +1 It's usually best to avoid pagination on the latest block. In Cardano, small rollbacks of 1~2 block are very frequent and expected (read Ouroboros for why) That means that using this block for pagination will often lead to your pagination being invalidated by a rollback To avoid this, you can pass an `offset` from the tip for more stable pagination

## Response `200`

- BlockLatestResponse
  - `block` object, required
    - `slot` number, double, required
    - `epoch` number, double, required
    - `height` number, double, required
    - `hash` string, required
    - `era` number, double, required

## Other responses

- `400`
- `428`

## Changes

- **2022-05-10** `f39bef51175a` — 3 info
  - added the non-success response with the status `428`
  - removed the non-success response with the status `409`
  - the `block/hash` response's property pattern `[0-9a-fA-F]{64}` was removed for the status `200`

[Change history](https://skmtc.dev/dcspark/apis/carp/changes/block/latest/post.md)

---

[API](https://skmtc.dev/dcspark/apis/carp.md) · [All operations](https://skmtc.dev/dcspark/apis/carp/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/dcspark/carp/revisions/f39bef51175a/schema)