# getSlot

> Returns the current slot the node has processed.

Source: https://docs.constant-k.com/rpc/http/getslot/

`getSlot` returns the most recent slot number at the requested commitment level. It's the simplest possible "where is the chain right now" check, and the basis for measuring how far behind (or ahead) other data is — compare a cached value against a fresh `getSlot` call to know how stale it's gotten.

- Transport: HTTP, JSON-RPC 2.0 `POST` to `https://rpc-newyork.constant-k.com/?api-key=YOUR_API_KEY` (New York) or `https://rpc-frankfurt.constant-k.com/?api-key=YOUR_API_KEY` (Frankfurt) or `https://rpc-amsterdam.constant-k.com/?api-key=YOUR_API_KEY` (Amsterdam). The key also works as an `x-api-key` header.
- Category: Slots & Epochs
- Availability: All plans
- Rate limits: Free 5/s · Operator 50/s · Blade Runner 200/s · Nexus 500/s

## Parameters

`params` is a positional JSON array, in this order:

- `config` (object, optional): Optional configuration.
  - `commitment` (string, optional, one of `finalized`, `confirmed`, `processed`, default `"finalized"`): Bank state to read the slot from. `processed` gives the newest slot the node has seen, at the cost of it possibly belonging to a fork that gets abandoned.
  - `minContextSlot` (integer, optional): Minimum slot the node must have processed before answering.

## Result

- `result` (integer, optional): Current slot number. A plain integer, not wrapped in a context/value envelope.

## Example: Get the current finalized slot

Request:

```bash
curl "https://rpc-newyork.constant-k.com/?api-key=YOUR_API_KEY" \
  -X POST \
  -H "Content-Type: application/json" \
  -d '{ "jsonrpc": "2.0", "id": 1, "method": "getSlot", "params": [] }'
```

Response:

```json
{
  "jsonrpc": "2.0",
  "result": 447951446,
  "id": 1
}
```

## Example: Get the current processed (newest, least confirmed) slot

Request:

```bash
curl "https://rpc-newyork.constant-k.com/?api-key=YOUR_API_KEY" \
  -X POST \
  -H "Content-Type: application/json" \
  -d '{
    "jsonrpc": "2.0",
    "id": 1,
    "method": "getSlot",
    "params": [{ "commitment": "processed" }]
  }'
```

Response:

```json
{
  "jsonrpc": "2.0",
  "result": 447951480,
  "id": 1
}
```

## Notes

- Mainnet-beta produces a new slot roughly every 270 ms (measured on our nodes in September 2026, and still falling), so treat any cached slot number as stale within a second.
- `processed` will typically read a little ahead of `finalized` — the gap is roughly the confirmation pipeline depth (usually well under 100 slots under normal conditions), not a fixed constant.