Validators
5
0.00% of the 938,993 indexed
Ethereum withdrawal address
0xff706a5b7a048c074fd425d0bb3f6556d509d703
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
Active
5
none exited
Effective stake
6.5K ETH
sum of effective balances
Slashed
0
5 compounding (0x02)
Validators
5 in this group
| Validator | Status | Effective balance |
|---|---|---|
| #2,278,9360xa28b4f0d…40a1011e | active | 1.8K ETH |
| #2,278,9390x8cf8f2b1…7ee8325c | active | 1.8K ETH |
| #2,278,9380x8de990d5…71d38fa8 | active | 1.7K ETH |
| #2,278,9400x84a5569b…876f1295 | active | 768.00 ETH |
| #2,278,9370xa869346a…5d185501 | active | 314.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