Loading
| Tx | Amount | Potential reward | Ends | Reward addr | Status |
|---|---|---|---|---|---|
| PSCo9GWijb…K5oo | 8,400 METAL | 112.27 METAL | in 50d 21h 5m | P-metal1czukwvr4lvxdg7qv23w9snqqerz3fv84d00m3l | active |
| Tx | Start | End | Stake | Reward | Status |
|---|---|---|---|---|---|
| 2HAhCxKNsRor…b4V5 |
| Oct 02, 2026, 1:23 AM UTC |
| Dec 02, 2026, 2:37 AM UTC |
| 2,100 METAL |
| 28.16 METAL |
| active |
| GS3hstGEBs8g…4kfm | Jul 15, 2026, 8:08 PM UTC | Sep 15, 2026, 8:20 PM UTC | 2,100 METAL | 31.8 METAL | ended |
| D9ZbXpTxpezn…AsiC | May 24, 2026, 9:39 PM UTC | Jul 14, 2026, 9:43 PM UTC | 2,102 METAL | 24.16 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.