Chains API

The newest validator withdrawals on Ethereum

The newest beacon-chain withdrawals credited on Ethereum (validator, receiver, amount, block) and the total number processed so far.

GET/api/external/chain-analysis/beacon-withdrawals/{chain}

Get a free API key Try it in the API reference

What it returns

The newest limit beacon-chain withdrawals credited on Ethereum, newest first: the withdrawal index, the validator it came from, the address credited, the amount in wei (a decimal string) and the block and time that carried it. totalWithdrawals is every withdrawal processed as of the newest indexed withdrawal — that index plus one, a count rather than an estimate because the index counts up by one per withdrawal from 0. Up to sixteen withdrawals land per 12-second slot, most of them small automatic reward skims; a 32 ETH-sized amount is usually a validator exiting.

Chains

Ethereum ETH

Request

Send your key in the x-dex-data-key header. Replace each <placeholder> with a real value.

curl -H "x-dex-data-key: $DEXDATA_API_KEY" \
  "https://api.dexdata.io/api/external/chain-analysis/beacon-withdrawals/ETH"

Parameters
Parameter	Description
`limit` query · integer · optional	How many withdrawals to return: 1 to 50. Defaults to 10. The ceiling is one source page; a short page returns fewer than asked rather than an error.
`chain` path · string · required	ETH only. Validator withdrawals are an Ethereum consensus-layer event; every other chain returns 400.

Response fields

A JSON response. Every field is always present; null means the value could not be established, never zero.

Response fields of The newest validator withdrawals on Ethereum
Field	Type	Description
`totalWithdrawals`	integer	Every withdrawal processed as of the newest indexed withdrawal: that index plus one. The index counts up by one per withdrawal, so this is a count rather than an estimate.
`withdrawals`	object[]	Newest first, one per withdrawal index, with no gaps.
`withdrawals[].index`	integer	The withdrawal index, counting up from 0 across the whole chain.
`withdrawals[].validatorIndex`	integer \| null	The validator the balance was withdrawn from, or null when not published.
`withdrawals[].receiver`	string \| null	The address credited (lower-case), or null when not published.
`withdrawals[].amountWei`	string \| null	The amount credited in wei, as a decimal string; null when not published.
`withdrawals[].blockNumber`	integer \| null	The block that carried the withdrawal.
`withdrawals[].timestamp`	integer \| null	Unix seconds of that block.

Price per call

Ethereum: 1 credit

Charged only when the call succeeds. Prices as of 2026-10-30; the current ones are always in the API reference.

The newest blocks on a chain
The blocks that carry these withdrawals.
The newest validator deposits on Ethereum
The other side of the same balance sheet: what leaves the beacon chain.
A block's validator withdrawals
The newest withdrawals chain-wide rather than the ones one named block paid out.
The validator withdrawals one wallet received
The same rows chain-wide, when the question is not about one address.
Is this compressed address still free, and what proves it
Says whether one address is still unused in a Solana ZK-compression address tree, and returns the non-inclusion proof — root, neighbours and Merkle path — a program needs to create it there.
What one Solana slot did
One named slot: whether its leader produced a block, who led it, its transactions split into votes and user traffic, how many failed, the fees paid, and for a recent slot the stake voted on it.

Start building with DexData today

Sign in, create a key and make your first call in a minute. Free credits every month, and you only pay for calls that succeed.

Get a free API key