← Network
Validator
8g9Duq7K…
NodeID-8g9Duq7Kvhpi5GeRq6TtEAFFLLDRin5XW
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
Jun 08, 2026, 3:04 AM UTC
End
Sep 08, 2026, 2:00 AM UTC
Tx hash
22WjH5Uunbtk1t…Zz4Q
Countdown
02
Months
19
Days
20
Hours
13
Minutes
06
Seconds
StartJun 08, 2026, 3:04 AM UTC
EndSep 08, 2026, 2:00 AM UTC
0%
13.17%
100%
Metal Primary Network Stake
Tx hash
22WjH5Uunbtk1t…Zz4Q
Validation reward addr
P-metal1cl24qy…l2ld
Delegation reward addr
P-metal1cl24qy…l2ld
Owned stake
9,999 METAL
Total stake
49,995 METAL
Network share
0.0368%
Available capacity
0 METAL
max 39,996 METAL (4× own)
Delegation
Delegator count
1
Delegation fee
5.00%
Delegator stake
39,996 METAL
Available capacity
0 METAL
Potential rewards
Owned validator stake rewards211.37 METAL100%
Delegation fee rewards0 METAL0%
Total rewards211.37 METAL
| Tx | Amount | Potential reward | Ends | Reward addr | Status |
|---|---|---|---|---|---|
| 2C8eyqeEKC…5WTv | 39,996 METAL | 745.91 METAL | in 79d 20h 13m | P-metal1kfjd07dt4m3fwe56vpe75wv9vnp90twcynlqvl | active |
Validating since
Jun 08, 2026, 3:04 AM UTC
Periods observed
1
Cumulative reward (potential + paid)
211.37 METAL
| Tx | Start | End | Stake | Reward | Status |
|---|---|---|---|---|---|
| 22WjH5Uunbtk…Zz4Q | Jun 08, 2026, 3:04 AM UTC | Sep 08, 2026, 2:00 AM UTC | 9,999 METAL | 211.37 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.