← Network
Validator
APSBdfqo…
NodeID-APSBdfqoJCSFkDAVJNXNy6mNk9G76LLeA
Running metalgo/1.12.2
Active · validating
Observed uptime
100.00%
Metal Primary Network Validation
Staking for
11111111111111111111…poYY
Status
active
Duration
6 months
Start
Apr 28, 2026, 2:49 PM UTC
End
Oct 25, 2026, 4:30 PM UTC
Tx hash
25WmikMiYBrad5…U39v
Countdown
05
Months
23
Days
12
Hours
49
Minutes
10
Seconds
StartApr 28, 2026, 2:49 PM UTC
EndOct 25, 2026, 4:30 PM UTC
0%
3.63%
100%
Metal Primary Network Stake
Tx hash
25WmikMiYBrad5…U39v
Validation reward addr
P-metal1qfe9v2…8we0
Delegation reward addr
P-metal1qfe9v2…8we0
Owned stake
7,000 METAL
Total stake
15,000 METAL
Network share
0.0114%
Available capacity
20,000 METAL
max 28,000 METAL (4× own)
Delegation
Delegator count
1
Delegation fee
5.00%
Delegator stake
8,000 METAL
Available capacity
20,000 METAL
Potential rewards
Owned validator stake rewards304.76 METAL100%
Delegation fee rewards0 METAL0%
Total rewards304.76 METAL
| Tx | Amount | Potential reward | Ends | Reward addr | Status |
|---|---|---|---|---|---|
| 2Lg1gN85BX…8mPn | 8,000 METAL | 344.08 METAL | in 173d 12h 49m | P-metal1e2fdkrrzqy0wyk9tvhjxqhzq324zaaqvp8rc5z | active |
Validating since
Apr 28, 2026, 2:49 PM UTC
Periods observed
1
Cumulative reward (potential + paid)
304.76 METAL
| Tx | Start | End | Stake | Reward | Status |
|---|---|---|---|---|---|
| 25WmikMiYBra…U39v | Apr 28, 2026, 2:49 PM UTC | Oct 25, 2026, 4:30 PM UTC | 7,000 METAL | 304.76 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.