← Network
Validator
5r4dCryj…
NodeID-5r4dCryjichmpEcZzv2BXySBp2tH93GXZ
Offline
Observed uptime
56.95%
Metal Primary Network Validation
Staking for
11111111111111111111…poYY
Status
active
Duration
21 days
Start
Apr 25, 2026, 9:25 PM UTC
End
May 16, 2026, 9:38 PM UTC
Tx hash
9TAVisfx1wnZTD…2Qmf
Countdown
00
Months
11
Days
17
Hours
54
Minutes
58
Seconds
StartApr 25, 2026, 9:25 PM UTC
EndMay 16, 2026, 9:38 PM UTC
0%
44.09%
100%
Metal Primary Network Stake
Tx hash
9TAVisfx1wnZTD…2Qmf
Validation reward addr
P-metal1mzu7u7…ywh4
Delegation reward addr
P-metal1mzu7u7…ywh4
Owned stake
4,755 METAL
Total stake
4,755 METAL
Network share
0.0036%
Available capacity
19,020 METAL
max 19,020 METAL (4× own)
Delegation
Delegator count
0
Delegation fee
4.00%
Delegator stake
0 METAL
Available capacity
19,020 METAL
Potential rewards
Owned validator stake rewards22.26 METAL100%
Delegation fee rewards0 METAL0%
Total rewards22.26 METAL
| Tx | Amount | Potential reward | Ends | Reward addr | Status |
|---|---|---|---|---|---|
| no delegators | |||||
Validating since
Dec 18, 2024, 4:10 PM UTC
Periods observed
20
Cumulative reward (potential + paid)
423.67 METAL
| Tx | Start | End | Stake | Reward | Status |
|---|---|---|---|---|---|
| 9TAVisfx1wnZ…2Qmf | Apr 25, 2026, 9:25 PM UTC | May 16, 2026, 9:38 PM UTC | 4,755 METAL | 22.26 METAL | active |
| 5rqY2c2s1G1x…iDpz | Mar 13, 2026, 8:42 PM UTC | Apr 03, 2026, 8:50 PM UTC | 4,735 METAL | 22.29 METAL | ended |
| faLdpPDj5qKV…kze9 | Feb 19, 2026, 2:23 AM UTC | Mar 12, 2026, 2:32 AM UTC | 4,710 METAL | 22.36 METAL | ended |
| fCYu7KYBcYHU…KbUQ | Jan 08, 2026, 4:30 PM UTC | Jan 29, 2026, 4:38 PM UTC | 4,690 METAL | 24.08 METAL | ended |
| UnY2ebsNNc8M…VXoR | Dec 13, 2025, 3:49 PM UTC | Jan 03, 2026, 3:57 PM UTC | 4,665 METAL | 23.94 METAL | ended |
| 2wRUCr3zA8fk…jt8p | Nov 19, 2025, 4:24 PM UTC | Dec 10, 2025, 4:33 PM UTC | 4,640 METAL | 22.18 METAL | ended |
| 2Li2me7CNeBi…uCU2 | Oct 28, 2025, 9:25 PM UTC | Nov 18, 2025, 9:33 PM UTC | 4,620 METAL | 23.68 METAL | ended |
| 8Nu6h3E8gpHk…6zME | Oct 07, 2025, 4:57 PM UTC | Oct 28, 2025, 5:05 PM UTC | 4,595 METAL | 22.07 METAL | ended |
| 2AQqQEpmfX4w…4zav | Sep 11, 2025, 8:00 PM UTC | Oct 02, 2025, 8:08 PM UTC | 4,575 METAL | 22.77 METAL | ended |
| jSaaL7CaV92G…b1Zn | Aug 20, 2025, 10:51 PM UTC | Sep 10, 2025, 10:59 PM UTC | 4,550 METAL | 24.65 METAL | ended |
| dT56P1kdRXEK…nQsF | Jul 21, 2025, 4:33 PM UTC | Aug 11, 2025, 4:41 PM UTC | 4,525 METAL | 22.56 METAL | ended |
| 2CN3hYEE31qY…Rv2M | Jun 28, 2025, 5:55 PM UTC | Jul 19, 2025, 6:01 PM UTC | 4,500 METAL | 24.5 METAL | ended |
| McrcEfkCrhUo…5S3o | Jun 05, 2025, 12:58 AM UTC | Jun 26, 2025, 1:03 AM UTC | 4,400 METAL | 21.96 METAL | ended |
| TpPHqcBd5pCA…NgCY | May 13, 2025, 10:00 PM UTC | Jun 03, 2025, 10:09 PM UTC | 4,450 METAL | 22.17 METAL | ended |
| zDo84JobD4KZ…pdpY | Apr 21, 2025, 11:33 PM UTC | May 12, 2025, 11:40 PM UTC | 4,400 METAL | 22 METAL | ended |
| RLv3iYmUm9i2…w24c | Mar 24, 2025, 1:44 AM UTC | Apr 14, 2025, 1:52 AM UTC | 4,000 METAL | 20.09 METAL | ended |
| QeYvykztCQgk…7pPA | Mar 03, 2025, 12:44 AM UTC | Mar 24, 2025, 12:51 AM UTC | 4,000 METAL | 20.1 METAL | ended |
| ainGwsSmsN9V…dm8C | Feb 09, 2025, 1:13 AM UTC | Mar 02, 2025, 1:21 AM UTC | 3,000 METAL | 17.48 METAL | ended |
| L8UXmgf4Kh55…kWJ5 | Jan 09, 2025, 3:48 PM UTC | Jan 30, 2025, 3:55 PM UTC | 2,000 METAL | 11.22 METAL | ended |
| prKRnEn4F39h…phGn | Dec 18, 2024, 4:10 PM UTC | Jan 08, 2025, 4:09 PM UTC | 2,000 METAL | 11.31 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? NO
- Connected to consensus peers?NO
- Currently in an active stake period?YES
- Earning rewards (uptime ≥ 80%)?NO
Responsiveness
56.95
0708090100
Network-observed uptime
56.95%
Connected to peers
no
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.