← Network
Validator
artwebin
NodeID-GepJFEB2m6sXzPqFnNDPAKALmR1j9hYhH
Running metalgo/1.13.5
Own this node? Update its name →Active · validating
Observed uptime
93.66%
Metal Primary Network Validation
Status
active
Duration
3 months
Start
Aug 04, 2026, 9:42 AM UTC
End
Oct 31, 2026, 11:00 AM UTC
Tx hash
2ero67FuzXtym8…XBSp
Countdown
02
Months
04
Days
07
Hours
37
Minutes
14
Seconds
StartAug 04, 2026, 9:42 AM UTC
EndOct 31, 2026, 11:00 AM UTC
0%
26.96%
100%
Metal Primary Network Stake
Tx hash
2ero67FuzXtym8…XBSp
Validation reward addr
P-metal1e6f2ww…4cha
Delegation reward addr
P-metal1e6f2ww…4cha
Owned stake
10,987 METAL
Total stake
54,935 METAL
Network share
0.0443%
Available capacity
0 METAL
max 43,948 METAL (4× own)
Delegation
Delegator count
1
Delegation fee
4.00%
Delegator stake
43,948 METAL
Available capacity
0 METAL
Potential rewards
Owned validator stake rewards218.2 METAL100%
Delegation fee rewards0 METAL0%
Total rewards218.2 METAL
| Tx | Amount | Potential reward | Ends | Reward addr | Status |
|---|---|---|---|---|---|
| 2reM1ZisLd…nY2s | 43,948 METAL | 266.64 METAL | in 16d 21h 36m | P-metal1ppydpt9v4cj96yjks0wjtf6lneuvyptdhcjg9f | active |
Validating since
Aug 04, 2026, 9:42 AM UTC
Periods observed
1
Cumulative reward (potential + paid)
218.2 METAL
| Tx | Start | End | Stake | Reward | Status |
|---|---|---|---|---|---|
| 2ero67FuzXty…XBSp | Aug 04, 2026, 9:42 AM UTC | Oct 31, 2026, 11:00 AM UTC | 10,987 METAL | 218.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
93.66
0708090100
Network-observed uptime
93.66%
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.