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

# 💎 MEV Timing per Day

> Returns the MEV timing-game statistics of a set of validators as a per-day series. The validator set may be selected by identifiers, dashboard or dashboard group, withdrawal credential or address, deposit address, or the entities that own or run them (`entities`). Each day covers the slots in which one of the validators proposed a block that came from a relay.

**Use case guide:** [Compare MEV Timing](/use-cases/compare-mev-timing) shows how to compare daily network, entity, and validator-set behavior.

**Protocol caveat:** The 1200 ms and 2600 ms timing bands apply to pre-Glamsterdam slots only. [Glamsterdam](https://ethereum.org/roadmap/glamsterdam/) introduces ePBS, and from its Gloas fork epoch on the arrival time of the winning relay bid no longer measures proposer timing. The series therefore ends at the fork: the fork day covers only its pre-fork slots, and later days are absent.

**Data provenance:** Timing statistics are derived from offchain relay APIs and streams. Relay-reported timestamps, identities, and bid coverage are not independently verifiable from onchain data; coverage gaps or inconsistent reporting can affect results.

**Validator set:** The selector is evaluated when you call the endpoint, and every day of the series counts the blocks of the validators it matches at that time. Dashboard, address and `entities` selectors therefore apply their current members to past days. A selector that matches no validator returns `404`. A day on which none of the validators proposed a block that came from a relay is absent from the series.

Results can be filtered by a time range (bucketed to whole UTC days) and are paginated, newest day first. For one histogram of the same validators over a fixed evaluation window, use [v2/ethereum/validators/mev-timing-aggregate](/api-reference/ethereum/validators/mev-timing-aggregate). For the whole network over the same days, use [v2/ethereum/mev-timing](/api-reference/ethereum/mev-timing).

**Note:** MEV relay and timing data is only available on mainnet at this time.

**History:** Relay bid collection began on 2024-06-03 (UTC). The series contains no days before that date; a time range that falls entirely before it returns an empty result.

Data freshness: a day appears about 4 to 5 hours after it ends, once the relay data of all its slots is aggregated; the current day is never included. Rows change only when relay data is reprocessed.

**Premium Endpoint:** This endpoint requires a Scale or Enterprise plan.




## OpenAPI

````yaml /v3/bundled.yaml post /api/v2/ethereum/validators/mev-timing
openapi: 3.0.4
info:
  title: External Service API
  version: 1.0.3
servers:
  - url: https://beaconcha.in
    description: Production API
security:
  - ApiKeyAuth: []
paths:
  /api/v2/ethereum/validators/mev-timing:
    post:
      tags:
        - Validator
      summary: 💎 MEV Timing per Day
      description: >
        Returns the MEV timing-game statistics of a set of validators as a
        per-day series. The validator set may be selected by identifiers,
        dashboard or dashboard group, withdrawal credential or address, deposit
        address, or the entities that own or run them (`entities`). Each day
        covers the slots in which one of the validators proposed a block that
        came from a relay.


        **Use case guide:** [Compare MEV Timing](/use-cases/compare-mev-timing)
        shows how to compare daily network, entity, and validator-set behavior.


        **Protocol caveat:** The 1200 ms and 2600 ms timing bands apply to
        pre-Glamsterdam slots only.
        [Glamsterdam](https://ethereum.org/roadmap/glamsterdam/) introduces
        ePBS, and from its Gloas fork epoch on the arrival time of the winning
        relay bid no longer measures proposer timing. The series therefore ends
        at the fork: the fork day covers only its pre-fork slots, and later days
        are absent.


        **Data provenance:** Timing statistics are derived from offchain relay
        APIs and streams. Relay-reported timestamps, identities, and bid
        coverage are not independently verifiable from onchain data; coverage
        gaps or inconsistent reporting can affect results.


        **Validator set:** The selector is evaluated when you call the endpoint,
        and every day of the series counts the blocks of the validators it
        matches at that time. Dashboard, address and `entities` selectors
        therefore apply their current members to past days. A selector that
        matches no validator returns `404`. A day on which none of the
        validators proposed a block that came from a relay is absent from the
        series.


        Results can be filtered by a time range (bucketed to whole UTC days) and
        are paginated, newest day first. For one histogram of the same
        validators over a fixed evaluation window, use
        [v2/ethereum/validators/mev-timing-aggregate](/api-reference/ethereum/validators/mev-timing-aggregate).
        For the whole network over the same days, use
        [v2/ethereum/mev-timing](/api-reference/ethereum/mev-timing).


        **Note:** MEV relay and timing data is only available on mainnet at this
        time.


        **History:** Relay bid collection began on 2024-06-03 (UTC). The series
        contains no days before that date; a time range that falls entirely
        before it returns an empty result.


        Data freshness: a day appears about 4 to 5 hours after it ends, once the
        relay data of all its slots is aggregated; the current day is never
        included. Rows change only when relay data is reprocessed.


        **Premium Endpoint:** This endpoint requires a Scale or Enterprise plan.
      operationId: GetValidatorMevTiming
      requestBody:
        $ref: '#/components/requestBodies/validatorMevTimingDaily'
      responses:
        '200':
          $ref: '#/components/responses/ValidatorMevTimingDaily'
        '400':
          $ref: '#/components/responses/BadRequest'
        '401':
          $ref: '#/components/responses/Unauthorized'
        '403':
          $ref: '#/components/responses/Forbidden'
        '404':
          $ref: '#/components/responses/NotFound'
        '405':
          $ref: '#/components/responses/MethodNotAllowed'
        '429':
          $ref: '#/components/responses/RateLimitExceeded'
        '500':
          $ref: '#/components/responses/InternalServerError'
        default:
          $ref: '#/components/responses/DefaultError'
components:
  requestBodies:
    validatorMevTimingDaily:
      x-go-name: ValidatorMevTimingDailyRequestBody
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/ValidatorMevTimingDailyRequest'
          example:
            validator:
              validator_identifiers:
                - 5
                - 6
            chain: mainnet
            page_size: 10
  responses:
    ValidatorMevTimingDaily:
      description: Successful response.
      content:
        application/json:
          schema:
            allOf:
              - $ref: '#/components/schemas/ValidatorMevTimingDaily.ContainerList'
              - $ref: '#/components/schemas/PagingRangeTemplate'
            description: >-
              Paginated response containing per-day MEV timing statistics for
              the selected validators.
    BadRequest:
      description: Bad Request
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/Error'
          example:
            error: Bad request. Please check your input and try again.
    Unauthorized:
      description: Unauthorized
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/Error'
          example:
            error: Unauthorized. Please provide a valid API key.
    Forbidden:
      description: Forbidden
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/Error'
          example:
            error: >-
              endpoint not allowed for your subscription tier. upgrade your
              subscription at https://beaconcha.in/pricing.
    NotFound:
      description: Not Found
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/Error'
          example:
            error: The requested resource was not found.
    MethodNotAllowed:
      description: Method Not Allowed
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/Error'
          example:
            error: 'method not allowed: GET. all public API endpoints use POST.'
    RateLimitExceeded:
      description: Rate Limit Exceeded
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/Error'
          example:
            error: Rate limit exceeded. Please try again later.
    InternalServerError:
      description: Internal Server Error
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/Error'
          example:
            error: internal server error. please try again later.
    DefaultError:
      description: An unexpected error response.
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/Error'
          example:
            error: An unexpected error occurred.
  schemas:
    ValidatorMevTimingDailyRequest:
      type: object
      properties:
        chain:
          $ref: '#/components/schemas/Chain'
        validator:
          $ref: '#/components/schemas/validatorsSelector'
        range:
          $ref: '#/components/schemas/timeRangeSelectorNullable'
        cursor:
          $ref: '#/components/schemas/Cursor'
        page_size:
          $ref: '#/components/schemas/PremiumMevTimingPageSize'
      required:
        - validator
    ValidatorMevTimingDaily.ContainerList:
      type: object
      properties:
        data:
          type: array
          items:
            $ref: '#/components/schemas/ValidatorMevTimingDaily.Data'
      required:
        - data
    PagingRangeTemplate:
      type: object
      properties:
        paging:
          $ref: '#/components/schemas/Paging'
        range:
          $ref: '#/components/schemas/ResultRange'
      required:
        - range
    Error:
      type: object
      properties:
        error:
          type: string
    Chain:
      type: string
      enum:
        - mainnet
        - hoodi
      default: mainnet
      description: The Ethereum chain to query.
    validatorsSelector:
      description: >-
        Free selectors available to all users:

        - validator_identifiers: One or more validator indices or public keys to
        filter by.

        - dashboard_id: Your beaconcha.in dashboard ID (requires a free
        account).
          
        **Premium selectors** for Scale & Enterprise plans
        (https://beaconcha.in/pricing):

        - withdrawal: The validator's withdrawal credential or the Ethereum
        wallet address used for withdrawals.

        - deposit_address: The Ethereum wallet address used for the validator's
        deposit.

        - entity: The name of the assigned entity (e.g., "Lido", "Coinbase").
        Optionally include `sub_entity` for more specific filtering. Matching is
        case-sensitive. Deprecated: use `entities` instead; [Migrating to Owners
        and Operators](/api/owners-and-operators) gives the sunset date.

        - entities: The entity that owns the validators (`owner`), the one that
        runs them (`operator`), or both, each by `id` or `path`.


        Note: The set of validators matched by `deposit_address` and
        `withdrawal` selectors is updated once per epoch (~6.4 minutes). Newly
        deposited validators may take up to one epoch to appear in query
        results.


        Note: The set of validators matched by `entity` selector is updated once
        per day.


        Note: The set of validators matched by `entities` is refreshed hourly; a
        newly deposited validator, or one whose owner or operator changed, can
        take up to an hour to be matched.
          
      oneOf:
        - $ref: '#/components/schemas/ValidatorsByIdentifiers'
        - $ref: '#/components/schemas/ValidatorsByDashboard'
        - $ref: '#/components/schemas/ValidatorsByDeposit'
        - $ref: '#/components/schemas/ValidatorsByWithdrawal'
        - $ref: '#/components/schemas/ValidatorsByEntity'
        - $ref: '#/components/schemas/ValidatorsByOwnerOperator'
    timeRangeSelectorNullable:
      description: >
        Specify a time range using either Unix timestamps or epoch numbers. If
        left null, the API will query the entire available history of the
        selected validators.
      nullable: true
      default: null
      oneOf:
        - $ref: '#/components/schemas/timeRangeSelectorTime'
        - $ref: '#/components/schemas/timeRangeSelectorEpoch'
        - $ref: '#/components/schemas/timeRangeSelectorSlot'
    Cursor:
      type: string
      description: >-
        Cursor value for pagination. See our [pagination guide](/api/pagination)
        for more details.
      default: ''
    PremiumMevTimingPageSize:
      type: integer
      description: The number of days to return per page.
      minimum: 1
      maximum: 100
      default: 10
    ValidatorMevTimingDaily.Data:
      type: object
      description: >-
        MEV timing-game statistics of the selected validators aggregated over a
        single UTC day (`GetValidatorMevTiming`).
      properties:
        timestamp:
          allOf:
            - $ref: '#/components/schemas/timestamp'
          description: >-
            Unix timestamp (seconds) of the start of the day (00:00 UTC) this
            row covers.
        date:
          type: string
          format: date
          description: >-
            The day this row covers, as a `YYYY-MM-DD` string (UTC).
            Human-readable convenience alongside `timestamp`.
        slots_with_relay_winners:
          type: integer
          minimum: 0
          description: >-
            Number of slots that day proposed by the selected validators for
            which a relay bid won (the proposed block came from a relay).
            Mirrors `slots_with_relay_winners` on the network endpoint — both
            count slots with an identified winning relay bid. A slot whose
            winning bid has no recorded slot offset is counted here but in no
            histogram bucket, so on such a day this count exceeds the histogram
            sum.
        timing_breakdown:
          $ref: '#/components/schemas/MevTimingBreakdown'
        median_slot_offset_ms:
          type: number
          format: double
          nullable: true
          description: >-
            Median winning-bid slot offset (ms) across the selected validators'
            slots with a winning relay bid that day, or `null` if none of them
            carries an offset. For an even count, the mean of the two middle
            offsets.
        histogram:
          $ref: '#/components/schemas/MevTimingHistogram'
      required:
        - timestamp
        - date
        - slots_with_relay_winners
        - timing_breakdown
        - median_slot_offset_ms
        - histogram
    Paging:
      type: object
      properties:
        next_cursor:
          description: >-
            Cursor to the next page of results. See our [pagination
            guide](/api/pagination) for more details. If empty, there are no
            more pages to fetch.
          type: string
          example: eyJfc2FtcGxlX2N1cnNvciI6MTIzNDU2Nzg5MH0
    ResultRange:
      type: object
      description: >
        The time span actually covered by the returned results — from the first
        to the last matching data point — specified in slots, epochs, and Unix
        timestamps.


        This reflects the data that was found, not the range that was queried.
        When the response is `200` but no data is found, it falls back to the
        requested range, or to the full available history if no range was given.
        Some endpoints answer `404` instead when no data is found.


        For arbitrary (custom) time-range queries the queried range is expanded
        outward to whole UTC days, so the covered range may be wider than
        requested. As stated above, the reported range still reflects the data
        that was actually found — a touched UTC day with no data for the
        selected validators will not extend it.
      properties:
        slot:
          $ref: '#/components/schemas/SlotRange'
        epoch:
          $ref: '#/components/schemas/EpochRange'
        timestamp:
          $ref: '#/components/schemas/TimeRange'
      required:
        - slot
        - epoch
        - timestamp
    ValidatorsByIdentifiers:
      type: object
      title: Indices/Pubkeys
      properties:
        validator_identifiers:
          $ref: '#/components/schemas/validatorIndexPublicKeys'
      required:
        - validator_identifiers
    ValidatorsByDashboard:
      type: object
      title: Dashboard
      properties:
        dashboard_id:
          $ref: '#/components/schemas/dashboardID'
        group_id:
          $ref: '#/components/schemas/dashboardGroupID'
      required:
        - dashboard_id
    ValidatorsByDeposit:
      type: object
      title: 💎 Deposit
      properties:
        deposit_address:
          $ref: '#/components/schemas/ExecutionLayerAddress'
      required:
        - deposit_address
    ValidatorsByWithdrawal:
      type: object
      title: 💎 Withdrawal
      properties:
        withdrawal:
          $ref: '#/components/schemas/AddressOrCredential'
      required:
        - withdrawal
    ValidatorsByEntity:
      type: object
      title: 💎 Entity (deprecated)
      deprecated: true
      description: >-
        Select validators by their assigned entity (e.g., staking provider) and
        optionally a sub-entity. Entity and sub-entity names are matched exactly
        and are case-sensitive.
      properties:
        entity:
          type: string
          description: >
            **Deprecated:** this selector will be sunset on the date [Migrating
            to Owners and Operators](/api/owners-and-operators) gives. Until
            then, it keeps working, and responses to requests that use it carry
            `Deprecation` and `Sunset` headers. From the sunset on, these
            requests return `410 Gone`. Use the `entities` selector instead: it
            takes the entity that owns the validators (`owner`), the one that
            runs them (`operator`), or both. Entities can be named and grouped
            differently from the old ones; the `search` filter of
            [/api/v2/ethereum/entities/owners](/api-reference/ethereum/entities/owners)
            and
            [/api/v2/ethereum/entities/operators](/api-reference/ethereum/entities/operators)
            finds an entity by name. That page lists every change.


            The name of the entity to filter validators by (e.g., "Lido",
            "Coinbase"). Matching is case-sensitive; use the exact name as
            returned by the entities overview endpoint.
        sub_entity:
          type: string
          description: >
            Optional sub-entity name to further filter validators within the
            entity. Matching is case-sensitive; use the exact name as returned
            by the sub-entities overview endpoint.
      required:
        - entity
    ValidatorsByOwnerOperator:
      type: object
      title: 💎 Owner / Operator
      description: >
        Selects validators by entity: the one that owns them (`owner`), the one
        that runs them (`operator`), or both, in which case a validator must
        match both. `owner` takes an id or path from
        [/api/v2/ethereum/entities/owners](/api-reference/ethereum/entities/owners),
        `operator` one from
        [/api/v2/ethereum/entities/operators](/api-reference/ethereum/entities/operators).


        An entity includes the entities below it: `lido` selects every Lido
        validator, `lido/csm` only those of Lido › CSM.
      properties:
        entities:
          $ref: '#/components/schemas/EntitySelection'
      required:
        - entities
    timeRangeSelectorTime:
      type: object
      title: Unix Timestamp
      description: Range provided via Unix timestamp (inclusive)
      properties:
        timestamp:
          $ref: '#/components/schemas/timeRangeStartEnd'
      required:
        - timestamp
    timeRangeSelectorEpoch:
      type: object
      title: Epoch
      description: Range provided via epoch number
      properties:
        epoch:
          $ref: '#/components/schemas/epochRangeStartEnd'
      required:
        - epoch
    timeRangeSelectorSlot:
      type: object
      title: Slot
      description: Range provided via slot number
      properties:
        slot:
          $ref: '#/components/schemas/slotRangeStartEnd'
      required:
        - slot
    timestamp:
      type: integer
      minimum: 0
    MevTimingBreakdown:
      type: object
      description: >-
        Count of slots in each timing-game band over the covered period, derived
        from the histogram at the 1200 ms / 2600 ms thresholds (see
        `MevTimingStatus`). These thresholds apply to pre-Glamsterdam slots and
        may change for post-fork classifications.
      properties:
        on_time_mev:
          type: integer
          minimum: 0
          description: Slots whose winning bid arrived ≤ 1200 ms after slot start.
        timing_games:
          type: integer
          minimum: 0
          description: Slots whose winning bid arrived 1201–2600 ms after slot start.
        aggressive_tg:
          type: integer
          minimum: 0
          description: Slots whose winning bid arrived > 2600 ms after slot start.
      required:
        - on_time_mev
        - timing_games
        - aggressive_tg
    MevTimingHistogram:
      type: array
      description: >-
        Distribution of winning-bid slot offsets across 22 fixed buckets, in
        ascending order. The first bucket covers all offsets below 0 ms,
        followed by 20 buckets in 200 ms steps from 0 to 3800 ms, and a final
        bucket for all offsets at or above 4000 ms.
      items:
        $ref: '#/components/schemas/MevTimingBucket'
    SlotRange:
      type: object
      properties:
        start:
          $ref: '#/components/schemas/Slot'
        end:
          $ref: '#/components/schemas/Slot'
      required:
        - start
        - end
    EpochRange:
      type: object
      properties:
        start:
          $ref: '#/components/schemas/Epoch'
        end:
          $ref: '#/components/schemas/Epoch'
      required:
        - start
        - end
    TimeRange:
      type: object
      properties:
        start:
          $ref: '#/components/schemas/timestamp'
        end:
          $ref: '#/components/schemas/timestamp'
      required:
        - start
        - end
    validatorIndexPublicKeys:
      description: >
        An array containing either validator indices or public keys. Index and
        public key can be mixed in the same array.


        Subscribed users (Hobbyist and Scale tiers, and existing Business
        subscribers) can include up to 100 entries; free trial users and legacy
        subscription users (Sapphire, Emerald, Diamond) are limited to 20.
      type: array
      items:
        $ref: '#/components/schemas/validatorIndexPublicKey'
      minItems: 1
      maxItems: 100
    dashboardID:
      description: >
        beaconcha.in dashboard ID. You can find your dashboard ID in the URL of
        your dashboard page on beaconcha.in (e.g.,
        https://beaconcha.in/dashboard/12345).
      type: integer
      x-go-type: '*int'
      minimum: 0
    dashboardGroupID:
      description: >-
        Optional beaconcha.in dashboard group ID. If no group ID is provided,
        all validators in the dashboard are considered.
      type: integer
      minimum: 0
      nullable: true
    ExecutionLayerAddress:
      type: string
      pattern: ^0x[a-fA-F0-9]{40}$
      description: A standard Ethereum address (20-byte hex string with 0x prefix).
      example: '0x388C818CA8B9251b393131C08a736A67ccB19297'
    AddressOrCredential:
      type: string
      pattern: ^(0x)?[0-9a-fA-F]{40}$|^(0x)?0[012][0-9a-fA-F]{62}$
      description: >
        Either an execution layer address (20-byte hex string with 0x prefix) or
        a full 32-byte withdrawal credential.
    EntitySelection:
      type: object
      description: >-
        The entity that owns the validators, the entity that runs them, or both.
        With both, a validator must match both. An entity includes the entities
        below it.
      properties:
        owner:
          description: >-
            The entity that owns the validators, from
            [/api/v2/ethereum/entities/owners](/api-reference/ethereum/entities/owners).
          x-go-type-skip-optional-pointer: false
          allOf:
            - $ref: '#/components/schemas/EntityReference'
        operator:
          description: >-
            The entity that runs the validators, from
            [/api/v2/ethereum/entities/operators](/api-reference/ethereum/entities/operators).
          x-go-type-skip-optional-pointer: false
          allOf:
            - $ref: '#/components/schemas/EntityReference'
      additionalProperties: false
      minProperties: 1
    timeRangeStartEnd:
      type: object
      description: Unix timestamp range (inclusive)
      properties:
        start:
          $ref: '#/components/schemas/timestamp'
          example: 0
          description: Start Unix Timestamp
        end:
          $ref: '#/components/schemas/timestamp'
          example: 2147483647
          description: End Unix Timestamp
      required:
        - start
        - end
    epochRangeStartEnd:
      type: object
      description: Epoch range (inclusive)
      properties:
        start:
          $ref: '#/components/schemas/EpochSelector'
          description: Start Epoch
        end:
          $ref: '#/components/schemas/EpochSelector'
          description: End Epoch
      required:
        - start
        - end
    slotRangeStartEnd:
      type: object
      description: Slot range (inclusive)
      properties:
        start:
          $ref: '#/components/schemas/SlotSelector'
          description: Start Slot
        end:
          $ref: '#/components/schemas/SlotSelector'
          description: End Slot
    MevTimingBucket:
      type: object
      description: >-
        A single bar of the timing histogram. Buckets are 200 ms wide. The first
        bucket covers all offsets below 0 ms; the last covers all offsets at or
        above 4000 ms (reported with an upper bound of 4200 ms).
      properties:
        slot_offset_ms_min:
          type: integer
          description: >-
            Inclusive lower bound of the bucket, in milliseconds relative to
            slot start.
        slot_offset_ms_max:
          type: integer
          description: >-
            Exclusive upper bound of the bucket, in milliseconds relative to
            slot start.
        count:
          type: integer
          minimum: 0
          description: Number of slots whose winning bid offset falls in this bucket.
        max_value:
          allOf:
            - $ref: '#/components/schemas/wei'
          nullable: true
          description: >-
            Highest winning bid value observed in this bucket, or `null` if the
            bucket is empty.
      required:
        - slot_offset_ms_min
        - slot_offset_ms_max
        - count
        - max_value
    Slot:
      type: integer
      minimum: 0
      description: Slot by number.
    Epoch:
      type: integer
      minimum: 0
    validatorIndexPublicKey:
      oneOf:
        - $ref: '#/components/schemas/validatorIndex'
        - $ref: '#/components/schemas/validatorPublicKey'
    EntityReference:
      description: >-
        An entity, by `id` or by `path`. A merged entity selects the entity it
        was merged into.
      oneOf:
        - $ref: '#/components/schemas/EntityById'
        - $ref: '#/components/schemas/EntityByPath'
    EpochSelector:
      description: |
        Specify an epoch using one of the following methods.
        - epoch number
        - View: "latest", "finalized" 
      oneOf:
        - $ref: '#/components/schemas/EpochByNumber'
        - $ref: '#/components/schemas/EpochByChainView'
    SlotSelector:
      description: |
        Specify a slot using one of the following methods.
        - Slot number
        - Consensus layer block root
        - View: "latest", "finalized" 
      oneOf:
        - $ref: '#/components/schemas/SlotByNumber'
        - $ref: '#/components/schemas/SlotByConsensusLayerBlockRoot'
        - $ref: '#/components/schemas/SlotByChainView'
      default: latest
    wei:
      type: string
      description: Amount in wei (1 ETH = 10^18 wei)
      pattern: ^(0|-?[1-9][0-9]*)$
      example: '32000000000000000000'
    validatorIndex:
      description: Validator Index
      type: integer
      minimum: 0
    validatorPublicKey:
      type: string
      description: Public key of a validator
      pattern: ^0x[a-fA-F0-9]{96}$
      example: >-
        0xab6b6d826c14b6141e3406c5227ead15b133993195e96edc05fdeba998d0e0fd96e4ec5f47f6c9eec1558a59042c03d1
    EntityById:
      title: Id
      type: object
      properties:
        id:
          $ref: '#/components/schemas/EntityId'
      required:
        - id
    EntityByPath:
      title: Path
      type: object
      properties:
        path:
          $ref: '#/components/schemas/EntityPath'
      required:
        - path
    EpochByNumber:
      title: Number
      type: object
      properties:
        number:
          $ref: '#/components/schemas/Epoch'
      required:
        - number
    EpochByChainView:
      title: View
      type: object
      properties:
        view:
          allOf:
            - $ref: '#/components/schemas/ChainView'
          description: >
            - "latest": Refers to the most recent epoch, which may not yet be
            finalized.

            - "finalized": Refers to the latest epoch that has been finalized
            and is not subject to change.
      required:
        - view
    SlotByNumber:
      title: Number
      type: object
      properties:
        number:
          $ref: '#/components/schemas/Slot'
      required:
        - number
    SlotByConsensusLayerBlockRoot:
      title: Root
      type: object
      properties:
        root:
          $ref: '#/components/schemas/ConsensusLayerBlockRoot'
      required:
        - root
    SlotByChainView:
      title: View
      type: object
      properties:
        view:
          allOf:
            - $ref: '#/components/schemas/ChainView'
          description: >
            - "latest": Refers to the most recent slot, which may be subject to
            reorganization.

            - "finalized": Refers to the latest slot that has been finalized and
            is not subject to change.
      required:
        - view
    EntityId:
      type: integer
      minimum: 1
      description: >-
        An entity's `id`, as listed by
        [/api/v2/ethereum/entities/owners](/api-reference/ethereum/entities/owners)
        or
        [/api/v2/ethereum/entities/operators](/api-reference/ethereum/entities/operators).
      example: 4603
    EntityPath:
      type: string
      minLength: 1
      maxLength: 256
      description: >-
        An entity's `path`, its parent's path and its own segment joined by `/`
        (e.g. `lido/csm`). Segments are compared ignoring case, with every run
        of spaces or punctuation read as one hyphen, so `Lido / Simple DVT`
        matches `lido/simple-dvt`.
      example: lido/csm
    ChainView:
      type: string
      enum:
        - latest
        - finalized
      description: >
        - "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.
    ConsensusLayerBlockRoot:
      type: string
      pattern: ^0x[a-fA-F0-9]{64}$
      description: A 32-byte block root represented as a hex string with 0x prefix.
  securitySchemes:
    ApiKeyAuth:
      type: http
      scheme: bearer
      description: >-
        Authorization header with value: Bearer YOUR_TOKEN. Refer to the [API
        Keys](/api/overview#api-keys) section to create your API key.

````

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