← Network
Validator
4qd383Gp…
NodeID-4qd383Gp8JNV9Ug4VeYsgp4y7dEa9BPkG
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 15, 2026, 3:46 PM UTC
End
Nov 15, 2026, 4:50 PM UTC
Tx hash
5z7hJbJzqbVJtz…P987
Countdown
02
Months
19
Days
13
Hours
26
Minutes
58
Seconds
StartAug 15, 2026, 3:46 PM UTC
EndNov 15, 2026, 4:50 PM UTC
0%
13.56%
100%
Metal Primary Network Stake
Tx hash
5z7hJbJzqbVJtz…P987
Validation reward addr
P-metal1980m5s…3fyg
Delegation reward addr
P-metal1980m5s…3fyg
Owned stake
2,051 METAL
Total stake
10,255 METAL
Network share
0.0083%
Available capacity
0 METAL
max 8,204 METAL (4× own)
Delegation
Delegator count
1
Delegation fee
4.00%
Delegator stake
8,204 METAL
Available capacity
0 METAL
Potential rewards
Owned validator stake rewards42.44 METAL100%
Delegation fee rewards0 METAL0%
Total rewards42.44 METAL
| Tx | Amount | Potential reward | Ends | Reward addr | Status |
|---|---|---|---|---|---|
| 2YqR5HjpAN…Kxbq | 8,204 METAL | 49.77 METAL | in 16d 21h 37m | P-metal1ax5qfekydxhyk03vv7z2t0xh9ttqhzj9nwx7ut | active |
Validating since
Aug 15, 2026, 3:46 PM UTC
Periods observed
1
Cumulative reward (potential + paid)
42.44 METAL
| Tx | Start | End | Stake | Reward | Status |
|---|---|---|---|---|---|
| 5z7hJbJzqbVJ…P987 | Aug 15, 2026, 3:46 PM UTC | Nov 15, 2026, 4:50 PM UTC | 2,051 METAL | 42.44 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.