Loading
| Tx | Amount | Potential reward | Ends | Reward addr | Status |
|---|---|---|---|---|---|
| 2oYXXYMk1e…sFTw | 59.79 METAL | 0.48 METAL | in 2d 22h 20m | P-metal1v9zy0qyk5urut0tuq30duzqp2wa4e0aehrxe85 | active |
| z2VBCxtRid…amFG | 31 METAL | 0.53 METAL | in 17d 22h 20m | P-metal1f2p4g3japr7fgyr00mmk2nc2rzp746qz2wqw5v | active |
| QJzHBZdp69…cBEu | 250 METAL | 4.1 METAL | in 17d 22h 37m | P-metal14uhah0glah7e0340t86ey5m897v3j7a4wx3sx9 | active |
| d932Avpxeo…qPuB | 235.72 METAL | 4.72 METAL | in 18d 22h 38m | P-metal14u0ee3dyg2ta2kue5wwe268vg5xqk7ra5pl3m7 | active |
| f4EdVWYov3…8Rbj | 25 METAL | 0.48 METAL | in 18d 22h 38m | P-metal1nz6386qkw2exc728ntq9ndysh2rw9twnynuzu6 | active |
| 2Vn5QcaY1E…jCmY | 395,000 METAL | 7,916.16 METAL | in 18d 22h 38m | P-metal1h7jw0tpz7vagdrnh3aev09m9h7l9rmy9c5uzaq | active |
| Tx | Start | End | Stake | Reward | Status |
|---|---|---|---|---|---|
| ojkBGkxPowoS…eGV5 | Aug 03, 2026, 4:05 AM UTC | Oct 31, 2026, 4:17 AM UTC | 98,901.5 METAL | 1,987.24 METAL | active |
| JKTXK7xuUfUu…awwu | May 02, 2026, 11:11 AM UTC | Jul 31, 2026, 7:11 AM UTC | 96,796.9 METAL | 2,104.68 METAL | ended |
| NV4Uj9HCszkc…haD8 | Jan 31, 2026, 8:32 AM UTC | Apr 30, 2026, 8:36 AM UTC | 94,614 METAL | 2,182.61 METAL | ended |
| 2ocywo8cRkYv…q31S | Oct 31, 2025, 3:46 AM UTC | Jan 31, 2026, 3:46 AM UTC | 82,513 METAL | 1,935.26 METAL | ended |
| cFpL8ZemEXHS…Yn1S | Sep 05, 2025, 8:02 AM UTC | Oct 31, 2025, 2:10 AM UTC | 62,526 METAL | 880.75 METAL | ended |
| i7QiP9aXCrNv…TTay | Aug 21, 2025, 7:11 AM UTC | Sep 04, 2025, 8:13 AM UTC | 2,000 METAL | 6.48 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.