← Network
Validator
Pr0F3$$0rDA0
NodeID-9szemz9BTZzTA1tUHv1sp7PodMYYn7Umq
Running metalgo/1.12.2
Active · validating
Observed uptime
100.00%
Metal Primary Network Validation
Staking for
11111111111111111111…poYY
Status
active
Duration
6 months
Start
Apr 05, 2026, 6:38 PM UTC
End
Oct 05, 2026, 4:00 PM UTC
Tx hash
2FXzCeoqSsvXHY…CVY5
Countdown
05
Months
03
Days
12
Hours
16
Minutes
25
Seconds
StartApr 05, 2026, 6:38 PM UTC
EndOct 05, 2026, 4:00 PM UTC
0%
16.06%
100%
Metal Primary Network Stake
Tx hash
2FXzCeoqSsvXHY…CVY5
Validation reward addr
P-metal19pjfw8…3v4x
Delegation reward addr
P-metal19pjfw8…3v4x
Owned stake
5,001 METAL
Total stake
25,005 METAL
Network share
0.0191%
Available capacity
0 METAL
max 20,004 METAL (4× own)
Delegation
Delegator count
1
Delegation fee
5.00%
Delegator stake
20,004 METAL
Available capacity
0 METAL
Potential rewards
Owned validator stake rewards222.15 METAL100%
Delegation fee rewards0 METAL0%
Total rewards222.15 METAL
| Tx | Amount | Potential reward | Ends | Reward addr | Status |
|---|---|---|---|---|---|
| 247b1zJW9V…iT3A | 20,004 METAL | 287.02 METAL | in 33d 21h 16m | P-metal160v82c30zyf9qz5ywujqrar24sf0sm9346u9mr | active |
Validating since
Apr 05, 2026, 6:38 PM UTC
Periods observed
1
Cumulative reward (potential + paid)
222.15 METAL
| Tx | Start | End | Stake | Reward | Status |
|---|---|---|---|---|---|
| 2FXzCeoqSsvX…CVY5 | Apr 05, 2026, 6:38 PM UTC | Oct 05, 2026, 4:00 PM UTC | 5,001 METAL | 222.15 METAL | active |
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.
Validator checklist
Is my validator OK? YES
- Connected to consensus peers?YES
- Currently in an active stake period?YES
- Earning rewards (uptime ≥ 80%)?YES
Responsiveness
100.00
0708090100
Network-observed uptime
100.00%
Connected to peers
yes
Stake period
active
Observed uptime · last 24h
from network samplesAll 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.