Loading live view
Loading the latest available information.
Loading the latest available information.
Processor overview
5EFX9W4NXNFf…foRN5xhjMY5EFX9W4NXNFfHy94f2Bg7rFVUjH3BCAcxX6qjPfoRN5xhjMY30-minute target · 5-minute grace · a monitoring baseline, not a chain eligibility rule
The unfinished gap is time since the last confirmed heartbeat. It continues to grow when a device stops sending. A gap does not prove the phone is offline; source delays and unknown history are shown separately.
Expected count is an estimate for covered time at one heartbeat per 30 minutes. Extra submissions are not automatically failures.
Heartbeat cadence is a monitoring target, not an on-chain reward or slashing rule. Long gaps and extra submissions are observations, not a diagnosis. Unknown or unindexed time is excluded from comparisons.
Saved fleets are monitored automatically, including newly mapped processors. Verified fleets receive historical backfill first, followed by other saved fleets. The initial fill covers approximately 24 hours where retained indexed transactions can be verified; longer history builds going forward. Other viewed processors stay monitored for seven days after their most recent view, with up to 128 additional on-demand watches. Missing history remains unknown. Compact history is stored on our secondary server. Minute detail is retained for 72 hours; compact hourly counts for 30 days. Counts are preserved even when burst timestamp detail is capped. No full heartbeat payload history is stored by this feature.
Earnings are derived allocations of manager rewards, not direct payments to the processor. “After heartbeat fees” excludes deployment income, other fees, hardware and electricity. Missing fee or reward history stays unavailable.