PTC Slots
Returns the slots where the specified validators held a position on the Payload Timeliness Committee, grouped by slot. Each result shows a slot number, how many committee positions your validators held in that slot, and how many of those positions voted.
The Payload Timeliness Committee attests to whether a block’s execution payload was revealed on time. It exists from the Gloas fork onwards, so this endpoint returns no results for earlier slots and no history is backfilled.
Counts are committee positions, not validators. The committee is sampled with replacement, so one validator can hold more than one position in the same slot and each position votes independently.
PTC duties are unpaid: missing one carries no penalty and earns no reward. Treat these counts as a participation signal, not an earnings one.
Combine this endpoint with others for deeper insights:
- Consensus slot information:
v2/ethereum/slot
Note: This endpoint supports only finalized data at this time.
Authorizations
Body
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_entityfor more specific filtering. Matching is case-sensitive.
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.
- Indices/Pubkeys
- Dashboard
- 💎 Deposit
- 💎 Withdrawal
- 💎 Entity
The Ethereum chain to query.
mainnet, hoodi Cursor value for pagination. See our pagination guide for more details.
The number of items to return per page.
1 <= x <= 10Specify 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.
- Unix Timestamp
- Epoch
- Slot
Response
Successful response.
Response containing the payload timeliness committee positions the validators held, grouped by slot.
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 no data is found, it falls back to the requested range, or to the full available history if no range was given.
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.

