Loading
| Tx | Amount | Potential reward | Ends | Reward addr | Status |
|---|---|---|---|---|---|
| 2bBEAcHdjo…Nsas | 938.84 METAL | 5.67 METAL | in 23d 20h 43m | P-metal1ra86mp58h945v38nhzaqc8uf5ahn89f7le3v0n | active |
| 2JU9wDdET1…Ye75 | 299,061.16 METAL | 2,792.47 METAL | in 41d 18h 22m | P-metal16lhtjytelp39vp75wqasg64xxpfpf706qwynk3 | active |
| Tx | Start | End | Stake | Reward | Status |
|---|---|---|---|---|---|
| 26jDVWognb7j…hxSu | Oct 03, 2026, 4:19 AM UTC | Jan 31, 2027, 5:20 AM UTC | 75,000 METAL | 2,039.08 METAL | active |
| BY23qea1cEve…Rugf | Jun 05, 2026, 3:23 AM UTC | Oct 01, 2026, 3:19 AM UTC | 25,187 METAL | 820.53 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.