← Network
Validator
2evtNF8x…
NodeID-2evtNF8xVYodkWkYzxqz8Sewm6EhXhQiP
Running metalgo/1.13.5
Name update pending review: “$COMPOUND$”
Offline
Observed uptime
82.55%
Metal Primary Network Validation
Status
active
Duration
6 months
Start
Jun 14, 2026, 5:55 PM UTC
End
Dec 25, 2026, 6:01 PM UTC
Tx hash
2cc49r4wZTk8bn…zitC
Countdown
03
Months
29
Days
14
Hours
35
Minutes
42
Seconds
StartJun 14, 2026, 5:55 PM UTC
EndDec 25, 2026, 6:01 PM UTC
0%
38.35%
100%
Metal Primary Network Stake
Tx hash
2cc49r4wZTk8bn…zitC
Validation reward addr
P-metal1fmsr2s…vtqe
Delegation reward addr
P-metal1fmsr2s…vtqe
Owned stake
2,064 METAL
Total stake
10,320 METAL
Network share
0.0083%
Available capacity
0 METAL
max 8,256 METAL (4× own)
Delegation
Delegator count
1
Delegation fee
4.50%
Delegator stake
8,256 METAL
Available capacity
0 METAL
Potential rewards
Owned validator stake rewards96.87 METAL100%
Delegation fee rewards0 METAL0%
Total rewards96.87 METAL
| Tx | Amount | Potential reward | Ends | Reward addr | Status |
|---|---|---|---|---|---|
| 2CKaQjYeox…mzaK | 8,256 METAL | 387 METAL | in 119d 14h 35m | P-metal1d4e8h6lxwsvelll859rvdggvjfy2q2tet3exem | active |
Validating since
Jun 14, 2026, 5:55 PM UTC
Periods observed
1
Cumulative reward (potential + paid)
96.87 METAL
| Tx | Start | End | Stake | Reward | Status |
|---|---|---|---|---|---|
| 2cc49r4wZTk8…zitC | Jun 14, 2026, 5:55 PM UTC | Dec 25, 2026, 6:01 PM UTC | 2,064 METAL | 96.87 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? NO
- Connected to consensus peers?NO
- Currently in an active stake period?YES
- Earning rewards (uptime ≥ 80%)?YES
Responsiveness
82.55
0708090100
Network-observed uptime
82.55%
Connected to peers
no
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.