← Network
Validator
Funky 🐸
NodeID-Mx5sAvyf88ZTWT3aGCrVCtJgVAwX78WWA
Running metalgo/1.13.5
Own this node? Update its name →Active · validating
Observed uptime
99.84%
Metal Primary Network Validation
Status
active
Duration
6 months
Start
May 16, 2026, 10:24 PM UTC
End
Nov 21, 2026, 11:38 PM UTC
Tx hash
2r32bVAuvMquy5…uKNi
Countdown
02
Months
25
Days
20
Hours
11
Minutes
22
Seconds
StartMay 16, 2026, 10:24 PM UTC
EndNov 21, 2026, 11:38 PM UTC
0%
54.59%
100%
Metal Primary Network Stake
Tx hash
2r32bVAuvMquy5…uKNi
Validation reward addr
P-metal1gxvrl8…2zue
Delegation reward addr
P-metal1gxvrl8…2zue
Owned stake
3,299 METAL
Total stake
16,495 METAL
Network share
0.0133%
Available capacity
0 METAL
max 13,196 METAL (4× own)
Delegation
Delegator count
1
Delegation fee
5.00%
Delegator stake
13,196 METAL
Available capacity
0 METAL
Potential rewards
Owned validator stake rewards151.03 METAL100%
Delegation fee rewards0 METAL0%
Total rewards151.03 METAL
| Tx | Amount | Potential reward | Ends | Reward addr | Status |
|---|---|---|---|---|---|
| 2KyyfxREp2…uc3e | 13,196 METAL | 602.19 METAL | in 85d 20h 10m | P-metal1w03a48ecdxu80ugeeq8fesun0xf2zduffppmsu | active |
Validating since
May 16, 2026, 10:24 PM UTC
Periods observed
1
Cumulative reward (potential + paid)
151.03 METAL
| Tx | Start | End | Stake | Reward | Status |
|---|---|---|---|---|---|
| 2r32bVAuvMqu…uKNi | May 16, 2026, 10:24 PM UTC | Nov 21, 2026, 11:38 PM UTC | 3,299 METAL | 151.03 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
99.84
0708090100
Network-observed uptime
99.84%
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.