← Network
Validator
4XwvAGwT…
NodeID-4XwvAGwTSTitLvWYWDLxaobSN9TZQkUdM
Running metalgo/1.13.5
Own this node? Update its name →Active · validating
Observed uptime
100.00%
Metal Primary Network Validation
Status
active
Duration
4 months
Start
May 02, 2026, 7:56 PM UTC
End
Aug 24, 2026, 3:48 AM UTC
Tx hash
i6s2TTvKv447M5…iwjx
Countdown
02
Months
04
Days
21
Hours
59
Minutes
01
Seconds
StartMay 02, 2026, 7:56 PM UTC
EndAug 24, 2026, 3:48 AM UTC
0%
42.72%
100%
Metal Primary Network Stake
Tx hash
i6s2TTvKv447M5…iwjx
Validation reward addr
P-metal18luh3z…zxqy
Delegation reward addr
P-metal18luh3z…zxqy
Owned stake
2,071 METAL
Total stake
8,632 METAL
Network share
0.0064%
Available capacity
1,723 METAL
max 8,284 METAL (4× own)
Delegation
Delegator count
1
Delegation fee
5.00%
Delegator stake
6,561 METAL
Available capacity
1,723 METAL
Potential rewards
Owned validator stake rewards54.79 METAL100%
Delegation fee rewards0 METAL0%
Total rewards54.79 METAL
| Tx | Amount | Potential reward | Ends | Reward addr | Status |
|---|---|---|---|---|---|
| 2dp3aVNUEo…SuZQ | 6,561 METAL | 21.58 METAL | in 12d 18h 36m | P-metal13kacgacsagsfmnn56twua4272wvpu898sm0m7z | active |
Validating since
May 02, 2026, 7:56 PM UTC
Periods observed
1
Cumulative reward (potential + paid)
54.79 METAL
| Tx | Start | End | Stake | Reward | Status |
|---|---|---|---|---|---|
| i6s2TTvKv447…iwjx | May 02, 2026, 7:56 PM UTC | Aug 24, 2026, 3:48 AM UTC | 2,071 METAL | 54.79 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.