Skip to content

Ethereum withdrawal address

0x64e49b3924ce10aebc53863b02c91e6669cb1e77

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

115

0.01% of the 938,474 indexed

Active

115

none exited

Effective stake

134.4K ETH

sum of effective balances

Slashed

0

76 compounding (0x02)

Validators

115 in this group

1–50 of 115 validators

Validators withdrawing to 0x64e49b3924ce10aebc53863b02c91e6669cb1e77
ValidatorStatusEffective balance
#2,288,6840x8e8e7877…6855d35factive1.9K ETH
#2,332,8030x865660b5…c673f9a9active1.9K ETH
#2,332,8450x84cbd116…e1cdfac5active1.9K ETH
#2,332,9390xb9ff90c3…62840a5bactive1.9K ETH
#2,333,0590xadee06d1…c711c3adactive1.9K ETH
#2,332,8090xb295b180…dbd2593dactive1.9K ETH
#2,332,8160xab45438a…dfeb7f6factive1.9K ETH
#2,332,8230xaf28faa3…15ec42e8active1.9K ETH
#2,332,8290xa0b7aa54…50f871e4active1.9K ETH
#2,332,8320xa8924335…73f129ccactive1.9K ETH
#2,332,8490xa02160dd…e06465dbactive1.9K ETH
#2,332,9640xa7c03d88…6a5c4ff9active1.9K ETH
#2,332,9700xb6c5133f…e5f04743active1.9K ETH
#2,332,9760xa85e20b6…268d9420active1.9K ETH
#2,332,9940xa01abeb9…bcdb349cactive1.9K ETH
#2,333,0420x8c651baa…105eca9dactive1.9K ETH
#2,333,0650x89f03b9d…40af9440active1.9K ETH
#2,333,0720xb29b5bf0…e320bcd4active1.9K ETH
#2,333,0770xb8b42644…93ff63d2active1.9K ETH
#2,333,0800xa59cf167…955fb87aactive1.9K ETH
#2,333,0950xa3617df6…ed2f952dactive1.9K ETH
#2,333,1840x977162ba…6e7db490active1.9K ETH
#2,333,1890x94600c79…2a6102f5active1.9K ETH
#2,333,3330xb5c5c0a8…e9e4e07dactive1.9K ETH
#2,333,3380x8a5dc516…3136abf8active1.9K ETH
#2,333,3500x8426a73b…62927ef2active1.9K ETH
#2,333,3550xae839f3b…a0c9eda7active1.9K ETH
#2,333,3600x9525673e…1d68ccddactive1.9K ETH
#2,333,9130xaf227ede…612f27b7active1.9K ETH
#2,333,9520xb89af5a3…3d50724aactive1.9K ETH
#2,333,9530x95ed8848…b4d8ddbbactive1.9K ETH
#2,333,9690x8d815f95…8f2f8bc3active1.9K ETH
#2,334,0210x9248f458…149d2ddfactive1.9K ETH
#2,334,0540xaaf86dd3…79d8ee50active1.9K ETH
#2,334,1770x89b4343e…08a164feactive1.9K ETH
#2,334,2040x864ac07c…3233ae82active1.9K ETH
#2,334,2490x8fb04db3…e904d57dactive1.9K ETH
#2,335,5370xa59fc038…032a30f0active1.9K ETH
#2,335,5880xb226d687…6fbbbd55active1.9K ETH
#2,335,6040xa38375d0…9444fceaactive1.9K ETH
#2,335,6130xb8dafc2b…a79e55c7active1.9K ETH
#2,335,6200xadc59265…b405080bactive1.9K ETH
#2,335,6220xa21327a9…5ebf3416active1.9K ETH
#2,335,6320xaefcd32e…15c180bfactive1.9K ETH
#2,335,6710xacda1e53…361c6460active1.9K ETH
#2,335,7330xb2a31ef3…98a85770active1.9K ETH
#2,335,7560xaf65de78…5b9ee94aactive1.9K ETH
#2,335,7640xab8103cd…368299adactive1.9K ETH
#2,335,7700xae496d0a…525b65cbactive1.9K ETH
#2,335,8580x844767ac…59185898active1.9K 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