Loading
| Tx | Amount | Potential reward | Ends | Reward addr | Status |
|---|---|---|---|---|---|
| 2ufDbt5Cne…STtf | 139,628 METAL | 1,276.03 METAL | in 27d 18h 23m | P-metal1hwu97lh3lpq9uregqfjj90vm6u6stz0nwfnk02 | active |
| 2BP1eoJbzx…vM86 | 21,696 METAL | 761.05 METAL | in 79d 23h 21m | P-metal1w03a48ecdxu80ugeeq8fesun0xf2zduffppmsu | active |
| Tx | Start | End | Stake | Reward | Status |
|---|---|---|---|---|---|
| 5pRcSnL58VrM…9nZp | Aug 02, 2026, 3:43 PM UTC | Dec 31, 2026, 4:56 PM UTC | 40,331 METAL | 1,419.88 METAL | active |
| 277aN6jp2Rtu…TSEb | May 15, 2026, 10:46 PM UTC | Aug 01, 2026, 3:54 PM UTC | 3,958 METAL | 81.49 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.