← Network
Validator
H8SRICHGRIND
NodeID-CTPMYPKGw5FvnsDWSQXsfXkdPbeBYD7U1
Running metalgo/1.13.5
Own this node? Update its name →Active · validating
Observed uptime
99.99%
Metal Primary Network Validation
Status
active
Duration
12 months
Start
May 31, 2026, 11:32 PM UTC
End
May 31, 2027, 11:00 AM UTC
Tx hash
TgnFwwdTJfuCmm…MrZq
Countdown
11
Months
15
Days
05
Hours
14
Minutes
54
Seconds
StartMay 31, 2026, 11:32 PM UTC
EndMay 31, 2027, 11:00 AM UTC
0%
5.28%
100%
Metal Primary Network Stake
Tx hash
TgnFwwdTJfuCmm…MrZq
Validation reward addr
P-metal1vd67w2…k2ku
Delegation reward addr
P-metal1vd67w2…k2ku
Owned stake
2,138 METAL
Total stake
10,690 METAL
Network share
0.0079%
Available capacity
0 METAL
max 8,552 METAL (4× own)
Delegation
Delegator count
1
Delegation fee
2.00%
Delegator stake
8,552 METAL
Available capacity
0 METAL
Potential rewards
Owned validator stake rewards204.85 METAL100%
Delegation fee rewards0 METAL0%
Total rewards204.85 METAL
| Tx | Amount | Potential reward | Ends | Reward addr | Status |
|---|---|---|---|---|---|
| 2UC8VUKMZb…JGn8 | 8,552 METAL | 420.3 METAL | in 185d 14h 14m | P-metal1jjmelk6phyvdyck88jm785pv2q0ph3yyghejq2 | ended |
Validating since
May 31, 2026, 11:32 PM UTC
Periods observed
1
Cumulative reward (potential + paid)
204.85 METAL
| Tx | Start | End | Stake | Reward | Status |
|---|---|---|---|---|---|
| TgnFwwdTJfuC…MrZq | May 31, 2026, 11:32 PM UTC | May 31, 2027, 11:00 AM UTC | 2,138 METAL | 204.85 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
99.99
0708090100
Network-observed uptime
99.99%
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.