# getMaxShredInsertSlot

> Returns the highest slot the node has inserted shreds for into its blockstore.

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

`getMaxShredInsertSlot` returns the highest slot for which the node has written incoming shreds into its local blockstore, regardless of whether that block has been assembled or replayed yet.

This is an operational signal, like `getMaxRetransmitSlot`, not something typical application code needs.

- 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

## Parameters

None.

## Result

- `result` (integer, optional): The highest slot with shreds inserted into the blockstore.

## Example: Get the highest shred-inserted 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": "getMaxShredInsertSlot" }'
```

Response:

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

## Notes

- Comparing it against `getMaxRetransmitSlot` and `getSlot` at the same moment can pinpoint whether a struggling node's bottleneck is shred receipt, retransmission, or replay.