← Network
Validator
Kellerkind_n1
NodeID-BEqGeE3BguhfmEBafAuMZvbHkFsurL3JQ
Running metalgo/1.13.5
Own this node? Update its name →Active · validating
Observed uptime
100.00%
Metal Primary Network Validation
Status
active
Duration
35 days
Start
Jul 26, 2026, 6:09 PM UTC
End
Aug 30, 2026, 6:00 PM UTC
Tx hash
2SEmqwtJBU5c1B…N2z8
Countdown
00
Months
02
Days
14
Hours
35
Minutes
15
Seconds
StartJul 26, 2026, 6:09 PM UTC
EndAug 30, 2026, 6:00 PM UTC
0%
92.55%
100%
Metal Primary Network Stake
Tx hash
2SEmqwtJBU5c1B…N2z8
Validation reward addr
P-metal1y5pd5y…umc5
Delegation reward addr
P-metal1y5pd5y…umc5
Owned stake
200,000 METAL
Total stake
507,051.48 METAL
Network share
0.4086%
Available capacity
492,948.52 METAL
max 800,000 METAL (4× own)
Delegation
Delegator count
7
Delegation fee
4.50%
Delegator stake
307,051.48 METAL
Available capacity
492,948.52 METAL
Potential rewards
Owned validator stake rewards1,543.18 METAL92%
Delegation fee rewards135.28 METAL8%
Total rewards1,678.45 METAL
| Tx | Amount | Potential reward | Ends | Reward addr | Status |
|---|---|---|---|---|---|
| M9bsuqWmHg…zYg1 | 18,854 METAL | 119.68 METAL | in 1d 10h 33m | P-metal13vgcmplhwcl5jmxmpa8qwzdy94r9py7jssqtw5 | active |
| 2ixvR6yj8e…BVMM | 44,913.77 METAL | 276.32 METAL | in 1d 15h 31m | P-metal1pz2v3gw2emlemqgwquytzf5y56psnzdjzn02vu | active |
| BPPX4KekcA…obwL | 25 METAL | 0.13 METAL | in 1d 20h 52m | P-metal1qq7uneam3jtx00l8qvayy3ywmsv5vfs8xsnsuu | active |
| 2A6R5m1716…LGKF | 42.72 METAL | 0.27 METAL | in 2d 3h 35m | P-metal1v9zy0qyk5urut0tuq30duzqp2wa4e0aehrxe85 | active |
| UNLhCwkKXZ…618p | 20,000 METAL | 137.48 METAL | in 2d 14h 34m | P-metal18nl4sap4rwaer00uqhgtzxzmtscmg6a5s0av5u | active |
| JCoiXe72cF…FTdP | 15,506 METAL | 102.73 METAL | in 2d 14h 35m | P-metal1jsyz0npysr9g643murch829ujfgqsfxd6tfh9s | active |
| 5CYJTRhhcb…wE9G | 207,709.98 METAL | 1,542.21 METAL | in 2d 14h 35m | P-metal1tgd4pd6lwzfaupr873s7wt93u7ll9wz3ju879t | active |
Validating since
Aug 14, 2024, 9:41 PM UTC
Periods observed
11
Cumulative reward (potential + paid)
41,633.04 METAL
| Tx | Start | End | Stake | Reward | Status |
|---|---|---|---|---|---|
| 2SEmqwtJBU5c…N2z8 | Jul 26, 2026, 6:09 PM UTC | Aug 30, 2026, 6:00 PM UTC | 200,000 METAL | 1,543.18 METAL | active |
| KAF571AJo8nw…Qnk5 | May 31, 2026, 8:02 PM UTC | Jul 26, 2026, 6:00 PM UTC | 200,000 METAL | 2,750.52 METAL | ended |
| 5kmivugka5Vq…kX2e | Sep 27, 2025, 6:16 PM UTC | May 31, 2026, 6:00 PM UTC | 200,000 METAL | 14,749.37 METAL | ended |
| 2DriPFMPpT3Q…qS3q | Mar 29, 2025, 7:45 PM UTC | Sep 27, 2025, 6:00 PM UTC | 200,000 METAL | 11,102.67 METAL | ended |
| 2sH4UT8VSxWE…S7Xp | Mar 02, 2025, 10:46 AM UTC | Mar 29, 2025, 7:00 PM UTC | 260,000 METAL | 1,709.56 METAL | ended |
| Tt2bLfMr47eA…rUr6 | Jan 25, 2025, 9:19 PM UTC | Mar 01, 2025, 7:00 PM UTC | 240,000 METAL | 2,504.34 METAL | ended |
| afmdBRDX5AFj…p6CW | Dec 21, 2024, 9:46 AM UTC | Jan 25, 2025, 7:00 PM UTC | 230,000 METAL | 2,259.65 METAL | ended |
| 6fJzZCtC68VY…Lcft | Nov 23, 2024, 10:00 PM UTC | Dec 20, 2024, 10:00 PM UTC | 200,000 METAL | 1,466 METAL | ended |
| ABCK4poC5mey…emfG | Oct 23, 2024, 9:13 PM UTC | Nov 23, 2024, 7:00 PM UTC | 130,000 METAL | 1,115.21 METAL | ended |
| 5MZUrNgDAFyJ…WyXn | Sep 18, 2024, 8:37 PM UTC | Oct 23, 2024, 6:00 PM UTC | 130,000 METAL | 1,184.99 METAL | ended |
| h6PSgyspsPi4…rwMh | Aug 14, 2024, 9:41 PM UTC | Sep 18, 2024, 6:00 PM UTC | 125,000 METAL | 1,247.57 METAL | ended |
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.