Skip to content

Ethereum withdrawal address

0x67e451f6836f63b34f2f673162be2e4ee6b05574

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

3

0.00% of the 967,165 indexed

Active

3

none exited

Effective stake

96.00 ETH

sum of effective balances

Slashed

0

no compounding credentials

Validators

3 in this group

3 validators

Validators withdrawing to 0x67e451f6836f63b34f2f673162be2e4ee6b05574
ValidatorStatusEffective balance
#65,9440x8f094523…84194c17active32.00 ETH
#65,9450xaf9dfe62…c254a73bactive32.00 ETH
#1,524,1810x8e8cde28…321c4462active32.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