getBlockProduction

getBlockProduction reports, per validator, how the leader schedule played out over a slot range on Solana — the Proof-of-History and Proof-of-Stake network secured by staked SOL. The response wraps a byIdentity map keyed by validator identity pubkey, where each entry is [leaderSlots, blocksProduced]: how many slots that validator was assigned as leader, and how many of those slots it actually produced a block for. The difference between the two is the validator's skip count. Without a range, the method covers the current epoch; you can also pass identity to filter to a single validator. Call it against https://solana.therpc.io/YOUR_API_KEY as a JSON-RPC 2.0 POST.

Use cases

• Measure a validator's skip rate by comparing leaderSlots against blocksProduced — the gap is how many assigned leader slots it missed.
• Rank validators by blocks produced across an epoch to compare performance for SOL delegation decisions.
• Spot underperforming leaders for a staking dashboard, flagging operators whose skip rate would erode delegators' rewards.

Parameters

Response

Example request

1curl https://solana.therpc.io/YOUR_API_KEY \
2  -X POST \
3  -H "Content-Type: application/json" \
4  -d '{
5  "jsonrpc": "2.0",
6  "id": 1,
7  "method": "getBlockProduction",
8  "params": [
9    {}
10  ]
11}'

Errors & troubleshooting

Common pitfalls

• With no range the method covers the entire current epoch, which can be a large span on Solana. Pass range with firstSlot and lastSlot to scope it to the window you actually care about.
• leaderSlots counts every slot the validator was scheduled to lead, including ones it skipped, so blocksProduced is often lower — that shortfall is the point of the metric, not an error.

Supported networks

• Mainnet
• Devnet

See also

• getLeaderSchedule
• getVoteAccounts