Skip to content

Ethereum withdrawal address

0xa6dd6a1cd0072a66e885c08484332b31e5272fa2

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

5

0.00% of the 965,526 indexed

Active

5

none exited

Effective stake

160.00 ETH

sum of effective balances

Slashed

0

no compounding credentials

Validators

5 in this group

5 validators

Validators withdrawing to 0xa6dd6a1cd0072a66e885c08484332b31e5272fa2
ValidatorStatusEffective balance
#2,9140x86bafab6…049ed193active32.00 ETH
#2,9150xb1aee932…8af83c64active32.00 ETH
#2,9160xa37e9eb5…838fba17active32.00 ETH
#2,9170xb1bda4d2…55a6a685active32.00 ETH
#14,8460x876780c9…d124f6c4active32.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