Loading
| Tx | Amount | Potential reward | Ends | Reward addr | Status |
|---|---|---|---|---|---|
| wVWXK4UcZR…t7KS | 3,149.5 METAL | 20.83 METAL | in 18d 16h 21m | P-metal15gsjexcnap4r9nuhwmg83h6w5ucf096zse37kr | active |
| 2QoLP2DgHY…UMpE | 159,850.5 METAL | 1,458.57 METAL | in 34d 18h 21m | P-metal17nck02q3j8qs3qe07slgcggs05r7wt0zvcq2ky | active |
| Tx | Start | End | Stake | Reward | Status |
|---|---|---|---|---|---|
| 29fDCQDZYHNK…5DMe | Aug 18, 2026, 12:29 AM UTC | Nov 18, 2026, 2:00 AM UTC | 40,750 METAL | 842.99 METAL | active |
| 2P2hGJ7XYroH…pYs9 | May 16, 2026, 2:22 AM UTC | Aug 16, 2026, 1:30 AM UTC | 27,974 METAL | 634.89 METAL | ended |
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.