---
title: "Slot"
method: POST
path: "/api/v2/ethereum/slot"
tags: ["Slot"]
---

# Slot

`POST /api/v2/ethereum/slot`

Returns detailed information about a specific consensus layer slot.

In Ethereum, "slots" are data containers on the consensus layer where validator duties are scheduled and blocks may be proposed. Each slot may reference a block, but a slot can also be missed.

This endpoint provides an overview of the requested slot, including its status (proposed, missed, scheduled), assigned proposer, participation metrics, protocol events (deposits, withdrawals, slashings), and other relevant details. 

You can query by slot number, block root hash, or use "latest" / "finalized" for the most recent or finalized slot.

## Request body

- object
  - `chain` 'mainnet' | 'hoodi' — The Ethereum chain to query.
  - `slot` union, required — Specify a slot using one of the following methods. - Slot number - Consensus layer block root - View: "latest", "finalized"
    - SlotByNumber
      - `number` integer, required — Slot by number.
    - SlotByConsensusLayerBlockRoot
      - `root` string, required — A 32-byte block root represented as a hex string with 0x prefix.
    - SlotByChainView
      - `view` 'latest' | 'finalized', required — - "latest": Refers to the most recent block, which may be subject to reorganization. - "finalized": Refers to the latest block that has been finalized and is not subject to change.

## Response `200`

Successful response.

- SlotOverviewContainer — Response containing basic information about the slot.
  - `data` SlotOverviewData, required — Overview statistics for a specific slot on the consensus layer. Note that a missed slot will be returned with minimal data (only slot number, epoch, timestamp, sync_committee_period and status).
    - `slot` integer, required — Slot by number.
    - `epoch` integer, required
    - `timestamp` integer, required
    - `execution_reference` ExecutionLayerReference — Reference to an execution layer block if one exists for the given slot. This will be null for missed slots.
      - `block` integer, required — Block by number.
      - `hash` string, required — A 32-byte block hash represented as a hex string with 0x prefix.
    - `proposer` Validator
      - `index` integer — Validator Index
      - `public_key` string — Public key of a validator
    - `status` 'success' | 'missed' | 'orphaned' | 'scheduled', required
    - `block_root` string — A 32-byte block root represented as a hex string with 0x prefix.
    - `parent_root` string — A 32-byte block root represented as a hex string with 0x prefix.
    - `state_root` string
    - `graffiti` string, nullable — Validators can include an optional message called "graffiti" in proposed blocks. The graffiti is limited to 32 bytes and is returned as a hex-encoded string here. If no graffiti was included, this field will be null.
    - `randao_reveal` string — A BLS signature represented as a hex string with 0x prefix.
    - `signature` string — A BLS signature represented as a hex string with 0x prefix.
    - `sync_committee_period` integer, required — The sync committee period number. Each sync committee period spans 256 epochs (approximately 27.3 hours with 6.4 minute epochs). The first sync committee period (period 290 on Ethereum Mainnet) started at the Altair hard fork on Oct 27, 2021, 10:56:23am UTC (epoch 74240).
    - `sync_participation` ValidatorSyncCommitteeDutyParticipation
      - `successful` integer, required — Number of times the validator successfully participated in the sync committee.
      - `assigned` integer, required — Number of times the validator has been assigned to participate in the sync committee, excluding missed slots.
      - `missed` integer, required — Number of times the validator missed participation in the sync committee, excluding missed network slots. The `missed` is always less than or equal to your actual `missed_including_missed_slots`.
      - `missed_including_missed_slots` integer, required — Number of times the validator missed participation in the sync committee, including missed network slots. Missed network slots are beyond your control. If this value is significantly higher than `missed`, it indicates that your validator is generally performing well, and most missed rewards are due to network issues rather than validator faults. However, if both `missed` and `missed_including_missed_slots` are high, it suggests potential issues with your validator's setup or connectivity, leading to missed sync committee messages.
      - `scheduled` integer, required — Number of scheduled sync committee votes for active and upcoming sync committees.
    - `attestation_participation` ValidatorAttestationDutyParticipation
      - `successful` integer, required — Number of validators that successfully attested on this slot.
      - `assigned` integer, required — Number of validators that were assigned to attest on this slot.
      - `missed` integer, required — Number of validators that missed attesting on this slot.
    - `queue_events` QueueEvents, nullable
      - `queued` QueueEventsQueued, required — Statistics about consensus layer events that were added to the queue in this slot.
        - `deposit` ClEventDetails, required
          - `count` integer, required
          - `amount` string, required — Amount in wei (1 ETH = 10^18 wei)
        - `withdrawal_manual` ClEventDetails, required
          - `count` integer, required
          - `amount` string, required — Amount in wei (1 ETH = 10^18 wei)
        - `consolidation` ClEventDetails, required
          - `count` integer, required
          - `amount` string, required — Amount in wei (1 ETH = 10^18 wei)
      - `processed` QueueEventsProcessed, required — Statistics about consensus layer events that were processed from the queue in this slot.
        - `deposit` ClEventDetails, required
          - `count` integer, required
          - `amount` string, required — Amount in wei (1 ETH = 10^18 wei)
        - `withdrawal_sweep` ClEventDetails, required
          - `count` integer, required
          - `amount` string, required — Amount in wei (1 ETH = 10^18 wei)
        - `withdrawal_manual` ClEventDetails, required
          - `count` integer, required
          - `amount` string, required — Amount in wei (1 ETH = 10^18 wei)
        - `consolidation` ClEventDetails, required
          - `count` integer, required
          - `amount` string, required — Amount in wei (1 ETH = 10^18 wei)
        - `voluntary_exit_count` integer, required — Number of voluntary exit requests that were processed from the exit queue in this slot.
    - `bls_credential_changes_count` integer, nullable — Number of BLS withdrawal credential changes included in this slot. A BLS withdrawal credential change allows a validator to update its withdrawal credentials from a BLS key to an execution address.
    - `included_slashing_count` IncludedSlashingCounts, nullable — Statistics about slashing proofs included in this slot. A slashing proof provides cryptographic evidence that one or more validators have committed a slashable offense.
      - `proposer` integer — Validator Index
      - `attestation` integer — Validator Index
    - `included_blob_commitment_count` integer, nullable — The count of data blobs commitments (kzg commitments) included in this slot, if present. Data blobs are introduced by EIP-4844 (Proto-Danksharding) as part of the data availability layer in the Pectra hardfork. This field is null for slots prior to the hardfork activation.
    - `finality` 'not_finalized' | 'finalized' — Indicates the finality status of the data provided. - Finalized data cannot be changed without slashing at least one-third of all validators, providing strong economic guarantees. - Data marked as not_finalized does not have this guarantee and may still change.

## Other responses

- `400` — Bad Request
- `401` — Unauthorized
- `403` — Forbidden
- `404` — Not Found
- `405` — Method Not Allowed
- `429` — Rate Limit Exceeded
- `500` — Internal Server Error
- `default` — An unexpected error response.

---

[API](https://skmtc.dev/beaconcha/apis/external-service-api.md) · [All operations](https://skmtc.dev/beaconcha/apis/external-service-api/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/beaconcha/external-service-api/revisions/ad26ad970b4e/schema)