Loading
| Tx | Amount | Potential reward | Ends | Reward addr | Status |
|---|---|---|---|---|---|
| auEhX65cCg…CzhY | 2,267.85 METAL | 116.77 METAL | in 85d 0h 27m | P-metal1nmva4mpkt9z07uxzc566u0ftyynhdcvpmqfcz6 | active |
| 22Fmco1dTq…es4b | 484.69 METAL | 21.53 METAL | in 85d 0h 27m | P-metal1gtekm7zsu5459vmszv5xs5556l2fmj0jwt4yz6 | active |
| 2farEeTp2Y…Znm6 | 6,231.46 METAL | 321.3 METAL | in 85d 0h 27m | P-metal1afru99zdsp5e99d8ng05jzw2thy5z7tfkndqau | active |
| Tx | Start | End | Stake | Reward | Status |
|---|---|---|---|---|---|
| 2kt2kaJmnhDv…4Fg3 | Jun 07, 2026, 10:45 PM UTC | Jan 05, 2027, 6:00 AM UTC | 2,246 METAL | 115.91 METAL | active |
Periods are recorded from when the collector started running. To extend history backwards, we'd backfill from platform.getRewardUTXOs against this validator's reward address.
All health data shown comes from the chain — observed by the rest of the network. Operator- private node telemetry (peer count, software version, bootstrap state) requires direct RPC access to the validator's machine and isn't surfaced here.