← Network
Validator
Metal 1
NodeID-7niT4uMcghW5VbGadKzFovSHxeA3JZtms
Running metalgo/1.13.5
Own this node? Update its name →Active · validating
Observed uptime
100.00%
Metal Primary Network Validation
Status
active
Duration
3 months
Start
May 29, 2026, 5:46 PM UTC
End
Aug 30, 2026, 5:55 PM UTC
Tx hash
2F6ME3NUD7r4dk…CpHG
Countdown
00
Months
02
Days
14
Hours
27
Minutes
28
Seconds
StartMay 29, 2026, 5:46 PM UTC
EndAug 30, 2026, 5:55 PM UTC
0%
97.20%
100%
Metal Primary Network Stake
Tx hash
2F6ME3NUD7r4dk…CpHG
Validation reward addr
P-metal1mfayrp…ny77
Delegation reward addr
P-metal1mfayrp…ny77
Owned stake
2,000 METAL
Total stake
7,500 METAL
Network share
0.0060%
Available capacity
2,500 METAL
max 8,000 METAL (4× own)
Delegation
Delegator count
1
Delegation fee
5.00%
Delegator stake
5,500 METAL
Available capacity
2,500 METAL
Potential rewards
Owned validator stake rewards42.85 METAL98%
Delegation fee rewards0.83 METAL2%
Total rewards43.68 METAL
| Tx | Amount | Potential reward | Ends | Reward addr | Status |
|---|---|---|---|---|---|
| 2Ute1D65Py…3czq | 5,500 METAL | 76.5 METAL | in 2d 14h 27m | P-metal10a03m08x5nekpn0r2uaz9mnnr0j0cytqkph573 | active |
Validating since
May 29, 2026, 5:46 PM UTC
Periods observed
1
Cumulative reward (potential + paid)
42.85 METAL
| Tx | Start | End | Stake | Reward | Status |
|---|---|---|---|---|---|
| 2F6ME3NUD7r4…CpHG | May 29, 2026, 5:46 PM UTC | Aug 30, 2026, 5:55 PM UTC | 2,000 METAL | 42.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
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.