← Network
Validator
MetalStream
NodeID-LAgGBxnduhFoG5p1fQQWhFTCFk8ZBLqys
Running metalgo/1.13.5
Own this node? Update its name →Active · validating
Observed uptime
100.00%
Metal Primary Network Validation
Status
active
Duration
2 months
Start
Apr 28, 2026, 4:06 PM UTC
End
Jun 28, 2026, 1:00 PM UTC
Tx hash
2dPy4RSSs4AHXp…FZkU
Countdown
00
Months
08
Days
05
Hours
38
Minutes
31
Seconds
StartApr 28, 2026, 4:06 PM UTC
EndJun 28, 2026, 1:00 PM UTC
0%
86.47%
100%
Metal Primary Network Stake
Tx hash
2dPy4RSSs4AHXp…FZkU
Validation reward addr
P-metal1t2vk3g…twne
Delegation reward addr
P-metal1t2vk3g…twne
Owned stake
2,207 METAL
Total stake
2,407 METAL
Network share
0.0018%
Available capacity
8,628 METAL
max 8,828 METAL (4× own)
Delegation
Delegator count
1
Delegation fee
5.00%
Delegator stake
200 METAL
Available capacity
8,628 METAL
Potential rewards
Owned validator stake rewards30.55 METAL98%
Delegation fee rewards0.58 METAL2%
Total rewards31.13 METAL
| Tx | Amount | Potential reward | Ends | Reward addr | Status |
|---|---|---|---|---|---|
| JWqh6wjVXK…hHhS | 200 METAL | 2.03 METAL | in 7d 20h 37m | P-metal1uqufnx380zzeezlmp3r03mnt0mazvt4xd8m7al | active |
Validating since
Apr 28, 2026, 4:06 PM UTC
Periods observed
1
Cumulative reward (potential + paid)
30.55 METAL
| Tx | Start | End | Stake | Reward | Status |
|---|---|---|---|---|---|
| 2dPy4RSSs4AH…FZkU | Apr 28, 2026, 4:06 PM UTC | Jun 28, 2026, 1:00 PM UTC | 2,207 METAL | 30.55 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.