Skip to content

Ethereum withdrawal address

0x01eb6fdf1fa7b14003159e62c74f640ab5c74f65

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

11

0.00% of the 938,818 indexed

Active

11

none exited

Effective stake

20.2K ETH

sum of effective balances

Slashed

0

11 compounding (0x02)

Validators

11 in this group

11 validators

Validators withdrawing to 0x01eb6fdf1fa7b14003159e62c74f640ab5c74f65
ValidatorStatusEffective balance
#2,275,9400x83463d1d…d642a128active1.9K ETH
#2,275,9420x8dcaf4b3…4e1a3bafactive1.9K ETH
#2,275,9440x8869539a…a9ae27f3active1.9K ETH
#2,275,9480x9777f307…814cb0afactive1.9K ETH
#2,275,9490xb5786731…356d1bebactive1.9K ETH
#2,275,9390x98868908…52441ccfactive1.9K ETH
#2,275,9410x8b8754b7…90fba7b7active1.9K ETH
#2,275,9430x977c335e…a7c8450aactive1.9K ETH
#2,275,9460x802017ed…289037e5active1.9K ETH
#2,275,9470xa1fec759…033ed403active1.9K ETH
#2,275,9450xadd04167…290a5482active798.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