← Network
Validator
paindoc
NodeID-PszWA7HQzm6TEGYBWQtjGDNMzWpS3M7ki
Running metalgo/1.13.5
Own this node? Update its name →Active · validating
Observed uptime
100.00%
Metal Primary Network Validation
Status
active
Duration
21 days
Start
Jun 02, 2026, 9:57 PM UTC
End
Jun 23, 2026, 10:06 PM UTC
Tx hash
ff3zanjB22AXgQ…agT9
Countdown
00
Months
03
Days
16
Hours
19
Minutes
18
Seconds
StartJun 02, 2026, 9:57 PM UTC
EndJun 23, 2026, 10:06 PM UTC
0%
82.48%
100%
Metal Primary Network Stake
Tx hash
ff3zanjB22AXgQ…agT9
Validation reward addr
P-metal1k4hz8r…kqxc
Delegation reward addr
P-metal1k4hz8r…kqxc
Owned stake
4,999 METAL
Total stake
19,231 METAL
Network share
0.0142%
Available capacity
5,764 METAL
max 19,996 METAL (4× own)
Delegation
Delegator count
1
Delegation fee
3.00%
Delegator stake
14,232 METAL
Available capacity
5,764 METAL
Potential rewards
Owned validator stake rewards23.26 METAL100%
Delegation fee rewards0 METAL0%
Total rewards23.26 METAL
| Tx | Amount | Potential reward | Ends | Reward addr | Status |
|---|---|---|---|---|---|
| 7cd5dDQmnh…UMnC | 14,232 METAL | 58.91 METAL | in 2d 16h 18m | P-metal1m93j9203s2e5rvmkr0gdycqrjy5k4fes6mpr86 | active |
Validating since
Jun 02, 2026, 9:57 PM UTC
Periods observed
1
Cumulative reward (potential + paid)
23.26 METAL
| Tx | Start | End | Stake | Reward | Status |
|---|---|---|---|---|---|
| ff3zanjB22AX…agT9 | Jun 02, 2026, 9:57 PM UTC | Jun 23, 2026, 10:06 PM UTC | 4,999 METAL | 23.26 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.