Acurast Pulse is a phone-farm-first explorer for the Acurast network. It gives managers, delegators, and operators real-time visibility into fleet health, staking posture, wallet balances, rewards, and on-chain activity.

Unlike a generic block explorer, Pulse is purpose-built for people running phone farms and staking on Acurast. Every page is designed to surface the data that matters most for operating and monitoring your infrastructure.

See in the full Acurast docs ↗

Phone farm operators who need to monitor device health, heartbeats, and earnings across their fleet.

Delegators who want to understand slash risk, pool health, and reward performance before choosing a manager.

Anyone participating in the Acurast network who wants clear, fast access to on-chain data without running their own indexer.

Acurast Pulse runs its own indexer against the Acurast chain. Most data is retained (indexed and stored locally) so pages load fast and reliably, even when the chain RPC is slow.

Fleet and operator-critical views prioritize freshness. Current balances are always exact. Historical data is retained selectively so the system can keep deeper history where the community actually uses it.

Most pages use retained indexed data that updates within seconds of block finalization. Fleet monitoring, heartbeat status, and balance snapshots stay as fresh as possible.

Some aggregate views (like staking leaderboards and phone earnings catalogs) are cached briefly to keep the site fast for everyone. You may see a short delay of 1-2 minutes on those pages.

A manager is an on-chain entity that operates a pool of processors (phones) on the Acurast network. Each manager has a unique numeric ID and an associated substrate wallet address.

Managers are responsible for keeping their processors online, processing heartbeats, and maintaining fleet health. Delegators stake to managers based on their performance and reliability.

See in the full Acurast docs ↗

Fleet pages are about device operations: which processors are up, their heartbeat status, deployment coverage, benchmark performance, and any reliability issues.

Staking pages are about delegation posture: how much is staked, commitment levels, reward accrual, slash risk, and pool health. They are related but answer different questions.

Fleet health shows the operational status of each processor in a manager's pool. Processors are marked as active (sending heartbeats on time), stale (heartbeat is late but not yet considered down), or down (no heartbeat received within the expected window).

A healthy fleet has most processors active with low heartbeat lag. If you see processors going stale or down, check the device's internet connection, app version, and whether the Acurast app is still running.

See in the full Acurast docs ↗

Heartbeat lag is the time since a processor's last heartbeat was recorded on-chain. Low lag (under a few minutes) means the device is healthy. High lag means the device may be offline, sleeping, or having connectivity issues.

Consistent heartbeat lag across multiple devices often points to a network or configuration issue rather than individual device problems.

See in the full Acurast docs ↗

The device editor lets you label processors with aliases (nicknames) and map them to phone models. This makes it much easier to manage a large fleet — instead of reading substrate addresses, you can identify each device by name and model.

Aliases are private to your farm and visible only to people with your management link or edit access token. Phone model mappings help you track which device models perform best.

Compare is a configurable chart workspace at /managers/<id>/compare. Pick up to 10 processors from the left rail, drop them into one or more chart cards, and compare them across compute score, heartbeat lag, active jobs, failures-per-hour, benchmarks, and (for telemetry-enabled fleets) battery, temperature, charging, and network state.

Each card has its own metric, range (24h / 7d / 30d), and processors. Add reference lines (median across a phone model), enable trend lines, pin the Y-axis range, and read per-series stats and anomaly flags under each chart. Click a row in the stats table to highlight that processor across every chart on the board.

Layouts are saved per-manager (verified managers save to backend, anonymous viewers save to localStorage) and you can keep multiple named views. Export any chart as PNG or CSV. Telemetry metrics only appear for managers whose fleet is enrolled in the telemetry stack.

Staking on Acurast involves delegating ACU tokens to a manager's pool. Your delegated tokens contribute to the pool's total stake, which affects the manager's eligibility for jobs and rewards.

Rewards are distributed per epoch (cycle) based on the pool's performance. The better a manager's processors perform (uptime, heartbeats, job completion), the more rewards the pool earns.

See in the full Acurast docs ↗

Slash risk measures the likelihood that a manager's pool could lose staked tokens due to poor performance. If processors consistently fail to send heartbeats or complete jobs, the protocol can slash (reduce) the pool's stake.

Acurast Pulse calculates slash risk based on current fleet health, heartbeat consistency, and historical performance. A low slash risk means the manager is operating reliably.

For the network-wide picture — daily slash timeline, top slashed managers, recent slash events with the burned/reward split, and a Slashing FAQ — see the /staking/slashing page.

See in the full Acurast docs ↗

Pool health is shown as a percentage representing the pool's current performance level. Higher percentages mean better performance.

Pool health is affected by processor uptime, heartbeat consistency, job completion rates, and the ratio of active processors to total processors in the pool.

See in the full Acurast docs ↗

Navigate to your manager's page and open the wallet trends section. You will see charts for balance history, epoch rewards (both accrued and paid), and heartbeat fee pressure over time.

The reward chart shows both accrued rewards (earned but not yet claimed) and paid rewards (transferred to your wallet). You can switch between 24-hour, 7-day, and 30-day views.

The Phone Earnings Catalog shows aggregated earning data by phone model across the entire Acurast network. It helps you understand which device models earn the most and how your fleet compares.

Data includes average daily earnings, top earner benchmarks, active processor counts, and historical earning trends per model. Use this to make informed decisions about which devices to add to your farm.

The APR page models the headline network yield for stakers: the gross annual return from the 70% staking share of inflation divided by current total staked ACU. It also shows trend charts so you can see how APR moves as total stake rises or falls.

The Calculator (also on the APR page) lets you compare running phones versus staking ACU for the same dollar budget. Pick a phone model from the catalog and a stake amount, and it side-by-sides expected monthly earnings, break-even timelines, and the dilution impact of more phones joining the network.

Below the trend charts there is a Trends FAQ with mini sketches that walk through what each curve shape means — what a delegator joining looks like, what a withdrawal looks like, and why APR and total stake move opposite each other.

See in the full Acurast docs ↗

The /network and /analytics/deployments pages show up to 6 months of retained history — supply, demand, total processors, deployed versus idle devices, and tier distribution. Depth increases as the indexer continues to retain daily snapshots.

Older periods can look thin because archive shard backfill is still in progress. Once backfill completes, historical charts will fill in.

The /apr page is the place to look for staking-specific history: 7-day and 30-day toggles for both Gross Network APR and Total Staked ACU, with mini-sketch explanations under the charts.

Conversion Preview is a read-only dashboard for verified farm managers that shows the current state of your token lock, the live conversion ratio, how much liquid ACU you'd receive if you converted right now, and how much you would forfeit.

It is a preview only — no wallet prompt, no extrinsic is ever submitted from the page. To actually convert you use the Acurast Hub signer flow.

A portion of ACU on manager owner accounts is held by the on-chain AcurastTokenConversion pallet. This freeze is applied at token migration and gradually unlocks over the full lock duration.

Frozen tokens are still yours. You can stake them and earn compute rewards while they remain locked. Rewards themselves are paid as liquid ACU and are fully claimable.

The ratio grows linearly from 0 at the lock start to 1 ACU : 1 ACU at the end of the total lock duration. Today's ratio is simply elapsed ÷ total.

If you convert now, you receive that fraction of your frozen amount as liquid ACU and the remainder is forfeited. The longer you wait, the more you receive on conversion.

The warmup is the minimum time tokens must stay locked before any unlock or conversion is permitted. Before warmup completes, the ratio is 0 and nothing can be withdrawn.

Once warmup has elapsed, you can either convert at the current ratio or keep waiting toward the full 1 ACU : 1 ACU unlock.

Early conversion gives you liquid ACU sooner but permanently forfeits the portion you haven't vested yet.

Waiting the full lock duration returns the ratio to 1 ACU : 1 ACU — your full frozen balance becomes liquid with no forfeit. The default recommendation is to wait unless you specifically need liquid ACU sooner.

Transferable balance is the amount you can freely send to another address. This is your available spending balance.

Locked balance is held by the protocol for staking commitments, vesting schedules, or governance participation. You still own these tokens but cannot transfer them until the lock expires.

Reserved balance is set aside for on-chain deposits (like registering a processor or placing a job). These tokens are returned when the deposit reason no longer applies.

Toggling Watch on a wallet tells Acurast Pulse to retain richer balance history for that account. Without watching, only recent balance snapshots are kept.

With watching enabled, you get deeper historical charts on the wallet trends page, including transferable balance over time, reward deposit markers, and withdrawal tracking. Use this for any farm wallet or account you want to monitor long-term.

Overview shows current balances, the linked manager context, and a summary of recent activity. It is the starting point for understanding an account's current state.

Trends shows charts over time: transferable balance history, per-epoch reward accrual, and heartbeat fee pressure. This is where you track performance across epochs.

Ledger shows the full transaction history: signed extrinsics, balance-affecting events, fee activity, and deployment-related movements. Use it when you need to find a specific transaction or audit activity.

Acurast Pulse indexes through archive nodes but retains per-account balance snapshots selectively to keep storage bounded. If a wallet was not being watched, historical balance snapshots may be sparse even though block history itself is available.

To build richer history going forward, enable Watch on the account from the Manage Saved Farms page or from the wallet overview. Acurast Pulse will begin retaining periodic balance snapshots from that point on.

Manage Saved Farms lets you save your phone farms for quick access, label processors with aliases, map devices to phone models, export fleet data as CSV, watch wallet balance history, and sync your farm list to other devices.

Think of it as your personal farm management dashboard within Acurast Pulse.

When you verify ownership of a phone farm, Acurast Pulse issues a unique edit access token stored in your browser. This token is the only way to prove you are the verified owner and grants you edit access to aliases, phone mappings, and fleet management for that farm.

Think of the edit access token like a private key. Anyone who has it can modify your farm data on Acurast Pulse. Never share it publicly, post it in group chats, or send it to anyone you do not trust.

Your edit access token is stored locally in your browser. It can be lost if you clear your browser data, reinstall your browser, or switch to a new device without transferring access first.

If your token is lost, there is no recovery option. Acurast Pulse does not store your token on the server and cannot restore it for you. You will need to re-verify ownership by completing the on-chain verification process again (sending the small verification transfer from the manager's owner wallet).

To avoid this: always use the Edit access link feature to transfer your token to another device or browser before clearing data or switching devices.

On a verified farm, tap Edit access link to generate a one-time link containing your owner token. Copy this link and open it on the target device or browser. The token will be imported automatically.

The link is sensitive. Treat it with the same care as a private key or password. Anyone who opens the link gains full edit access to your farm on Acurast Pulse.

A management link syncs your saved farm list, names, and labels to another device. It does not transfer edit access tokens for verified farms.

An edit access link transfers the owner token for a specific verified farm to another device. You need both if you want full access on another device: the management link for the farm list, then individual edit access links for each verified farm.

Click Verify ownership on your saved farm. Acurast Pulse generates a unique verification address and a small transfer amount.

From the owner wallet of the manager, send the exact requested amount to the verification address. Acurast Pulse watches the chain for the transfer. Once detected, ownership is confirmed and your browser receives the edit access token.

The transfer amount is small and is used solely to prove you control the owner wallet. This only needs to be done once per farm, unless you lose your token and need to re-verify.

Your token lives only in your browser and in any edit access links you generate. As long as you do not share those links publicly or let untrusted people access your browser, your edit access is secure.

If you suspect your token has been compromised, re-verify ownership of the farm. This issues a new token and invalidates the old one. The attacker's copy of the token will stop working.

The Blocks page shows finalized chain history in block order. Use it for event review, verifying when something happened on-chain, and exact block-level inspection.

The Extrinsics page lets you look up specific transactions by hash or browse recent extrinsics by type. Use it when you need to inspect a specific on-chain action or verify a transaction.

Search supports manager IDs, processor IDs, substrate wallet addresses, block numbers, extrinsic hashes, and job IDs. You can use partial addresses — search will match fragments.

Tip: if you know a manager ID, just type the number. If you have a substrate address, paste the full address or a fragment of it.

Retained means the data has been indexed from the chain and stored locally by Acurast Pulse. This makes pages fast and reliable, since the site does not need to query the chain RPC for every request.

Retained data is not stale or inaccurate — it is continuously updated as new blocks finalize. The term is used to distinguish from live RPC queries, which can be slow but always reflect the absolute latest chain state.

Some pages make their first load from the chain RPC, which can take several seconds. After the first load, the data is cached and subsequent visits will be much faster.

If a page is consistently slow, try refreshing after a few seconds. The cache will have been populated by your first request.

Acurast Pulse indexes data independently and may update at slightly different intervals than other explorers. Small differences in timing are normal.

For current balances and on-chain state, Acurast Pulse queries the chain directly and should match other sources. For historical aggregates (like total rewards or earning averages), different calculation windows or data retention policies can cause minor differences.

A processor shows as down when Acurast Pulse has not seen a heartbeat within the expected window. Common causes: the Acurast app was killed by the phone's battery optimization, the device lost internet connectivity, or the app needs to be updated.

Check that the Acurast app is still running in the foreground, battery optimization is disabled for the app, and the device has a stable internet connection. After the device sends its next heartbeat, the status will update automatically.

From the Manage Saved Farms page, expand a farm card and use the Export button. You can choose between three formats: processor IDs only, aliases only, or the full dataset (IDs, aliases, phone models, and status).

The export downloads as a CSV file that you can open in any spreadsheet application.

Yes. Acurast Pulse is fully responsive and works on phones and tablets. All features — fleet monitoring, staking, wallet tracking, farm management, and device editing — work on mobile browsers.

For the best experience managing a large fleet, a desktop browser gives you more screen space for the device grid and charts.

Each point is the headline yield: 70% of the annual emission divided by the total ACU staked at that moment, then annualized.

It tends to drift down over time because emissions are roughly fixed but total stake usually grows. Sharp moves almost always trace back to a stake event.

Daily snapshots of how much ACU is locked in staking across every active manager and delegator.

Steady upward drift is the normal pattern — managers compound rewards and new delegators come online. Step-changes mean a large account moved.

Gross APR is emissions ÷ total staked. Emissions are fixed, so when total stake rises the same pool gets sliced thinner.

Use the two charts side-by-side: a stake bump on the right chart usually shows up as a matching APR dip on the left.

You'll see a single-day step up in Total Staked ACU and a matching step down in Gross APR on the same date.

If the new stake is heavily concentrated in one manager, the Manager Distribution percentiles below also widen on that day.

The mirror image: Total Staked drops, and Gross APR pops up because remaining stakers split the same emission across a smaller base.

Withdrawals show up immediately at the protocol level — there is no warmup window for the network APR calculation.

When neither emission cadence nor total stake changes meaningfully, both lines stay flat — that is healthy, not a data gap.

The 7d toggle compresses the same data; if the 30d view is flat, the 7d view will be too.

A slash is an automatic protocol penalty when a manager's pool fails its on-chain commitments — usually missed heartbeats, missed reports, or a job that the assigned processor never completed.

It is enforced by the chain itself via the acurastCompute pallet, not by any human or governance vote. The Recent Slash Events feed is built from the resulting acurastCompute.Slashed events.

Each slash splits into two parts. Burned ACU is permanently removed from supply — it leaves the network. Reward ACU goes to the slot's reporter as a bounty for catching the failure.

On a typical slash about three quarters is burned and one quarter is paid out, but the exact ratio is set on-chain and can change. Add the two columns together to get the total slashed amount.

The chain sizes the slash from the offending pool's stake — bigger pools that miss commitments lose proportionally more ACU. It is not a flat fee.

The 'Largest single' KPI at the top of the page tracks the biggest individual event over the 30-day window so you can spot outliers without scrolling the feed.

Slashing is heavy-tailed in practice: most managers go a full 30 days with zero slashes, while a handful absorb the bulk of events because of a single bad week — devices going offline together, an app update breaking heartbeats, or a misconfigured pool.

The chart sorts by total slashed ACU rather than count so a single big event surfaces alongside chronic small ones.

Yes. Delegated stake is at risk alongside the manager's own stake — that is the whole point of delegation as a sybil-resistant signal. When the pool gets slashed, every delegator's share takes a proportional hit.

Your delegator APR on the /apr page already nets out historical slashing, so a manager that has been slashed regularly will show a lower realized return even if their headline operator APR looks healthy.

Slash events stop appearing in the feed, the timeline goes flat, and pool health on the manager's staking page climbs back. There is no explicit 'unslash' — already-burned ACU stays burned.

Use the daily timeline plus the manager-specific slash-risk view on /managers/<id>/delegation to confirm whether recent activity is a one-off incident or an ongoing problem.

Keep heartbeats consistent: stable connectivity, the latest Acurast app build, battery optimization disabled, and processors that aren't double-booked across managers.

Watch the /managers/<id>/fleet pages for processors stuck in 'watch' or 'down' state — those are the ones most likely to trigger the next slash. The Build column flags devices that have fallen behind the latest stable release.

Every event traces back to an acurastCompute.Slashed extrinsic finalized on-chain. The indexer records the block number, the commitment ID, the manager, and the burned/reward split exactly as the runtime emitted it.

Click any block number in the feed to inspect the original extrinsic. The 30-day numbers update within seconds of finalization — there is no separate aggregation lag.