← Network
Validator
DTdtdzgn…
NodeID-DTdtdzgnoMD2vevEYRiRuU3wfyKGhYTNB
Running metalgo/1.13.5
Own this node? Update its name →Active · validating
Observed uptime
99.96%
Metal Primary Network Validation
Status
active
Duration
3 months
Start
Aug 19, 2026, 10:00 PM UTC
End
Nov 18, 2026, 4:08 PM UTC
Tx hash
2grCmRTe6D9Zr8…dYFx
Countdown
02
Months
22
Days
12
Hours
45
Minutes
25
Seconds
StartAug 19, 2026, 10:00 PM UTC
EndNov 18, 2026, 4:08 PM UTC
0%
9.06%
100%
Metal Primary Network Stake
Tx hash
2grCmRTe6D9Zr8…dYFx
Validation reward addr
P-metal1x62jel…2j77
Delegation reward addr
P-metal1x62jel…2j77
Owned stake
2,002 METAL
Total stake
10,010 METAL
Network share
0.0081%
Available capacity
0 METAL
max 8,008 METAL (4× own)
Delegation
Delegator count
1
Delegation fee
5.00%
Delegator stake
8,008 METAL
Available capacity
0 METAL
Potential rewards
Owned validator stake rewards40.78 METAL100%
Delegation fee rewards0 METAL0%
Total rewards40.78 METAL
| Tx | Amount | Potential reward | Ends | Reward addr | Status |
|---|---|---|---|---|---|
| 2WwwTBAxKK…98Zn | 8,008 METAL | 159.32 METAL | in 82d 12h 45m | P-metal1a2ha27vzxy9m0fltp2lzzy99u0crft5ht7379m | active |
Validating since
Aug 19, 2026, 10:00 PM UTC
Periods observed
1
Cumulative reward (potential + paid)
40.78 METAL
| Tx | Start | End | Stake | Reward | Status |
|---|---|---|---|---|---|
| 2grCmRTe6D9Z…dYFx | Aug 19, 2026, 10:00 PM UTC | Nov 18, 2026, 4:08 PM UTC | 2,002 METAL | 40.78 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.96
0708090100
Network-observed uptime
99.96%
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.