Skip to content

Ethereum withdrawal address

0x9895d7a932afbc66e05e0e922c2ab90435bb5950

No operator is published for this withdrawal address. Ethereum validators carry no name on the beacon chain, and a label taken from a crowd-sourced explorer would be a guess about who controls stake.

Totals

Validators

204

0.02% of the 947,630 indexed

Active

204

none exited

Effective stake

6.5K ETH

sum of effective balances

Slashed

0

no compounding credentials

Validators

204 in this group

201–204 of 204 validators

Validators withdrawing to 0x9895d7a932afbc66e05e0e922c2ab90435bb5950
ValidatorStatusEffective balance
#1,199,2570x844ccbf4…4645e740active32.00 ETH
#1,199,2580xac8049d3…6dca0af8active32.00 ETH
#1,199,2590xaaf1a755…b050fda1active32.00 ETH
#1,850,8020x99386077…cba1b143active32.00 ETH

How this address was derived

An Ethereum validator’s withdrawal credentials are 32 bytes: a one-byte prefix, eleven zero bytes, then a twenty-byte execution address. Prefix 0x01 and 0x02 carry one; 0x00 is a BLS key with no execution address in it at all, and reading its last twenty bytes would produce an address that looks real and belongs to nobody.

The operator is named only where the address is a publicly documented protocol contract, with a link to the documentation. An explorer’s label is not enough: those are crowd-sourced, and attaching one here would publish a claim about who controls a large share of the stake on the basis of a wiki edit.

Full methodology