← Network
Validator
HUNLeDoh…
NodeID-HUNLeDohyYWYq8vqj6wcLr9SG8kEQ638w
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
Aug 03, 2026, 8:33 PM UTC
End
Nov 03, 2026, 9:44 PM UTC
Tx hash
2EGDSJHakTNbVW…3jzX
Countdown
02
Months
07
Days
18
Hours
20
Minutes
04
Seconds
StartAug 03, 2026, 8:33 PM UTC
EndNov 03, 2026, 9:44 PM UTC
0%
26.38%
100%
Metal Primary Network Stake
Tx hash
2EGDSJHakTNbVW…3jzX
Validation reward addr
P-metal1f7vvr3…l0ju
Delegation reward addr
P-metal1f7vvr3…l0ju
Owned stake
2,557 METAL
Total stake
6,648 METAL
Network share
0.0054%
Available capacity
6,137 METAL
max 10,228 METAL (4× own)
Delegation
Delegator count
1
Delegation fee
5.00%
Delegator stake
4,091 METAL
Available capacity
6,137 METAL
Potential rewards
Owned validator stake rewards53.2 METAL100%
Delegation fee rewards0 METAL0%
Total rewards53.2 METAL
| Tx | Amount | Potential reward | Ends | Reward addr | Status |
|---|---|---|---|---|---|
| rW4dhy8Zoh…dGhV | 4,091 METAL | 64.35 METAL | in 67d 18h 20m | P-metal18dm7unuj8aduq7ekdf6lpehzumwznqlhr6ajy4 | active |
Validating since
Aug 03, 2026, 8:33 PM UTC
Periods observed
1
Cumulative reward (potential + paid)
53.2 METAL
| Tx | Start | End | Stake | Reward | Status |
|---|---|---|---|---|---|
| 2EGDSJHakTNb…3jzX | Aug 03, 2026, 8:33 PM UTC | Nov 03, 2026, 9:44 PM UTC | 2,557 METAL | 53.2 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.