Phone Farm

Loading fleet overview

Streaming live processor telemetry, deployment assignments, and reward history for this manager.

Resolving route12%

Acurast Pulse

Loading live view

Syncing chain state, reward ledgers, and fleet telemetry.

Resolving route12%

Manager Phone Earnings #13319 | Acurast Pulse

#13319·5EMsBLso...MhGZFc·Phone Earnings

Staking

Farm payout

0.048883 ACU

epoch 3,734 · 17 hrs ago

Boost benefit

+0.004836 ACU

91.7% boosted · network 67.1%

11 of 12 devices · +27k compute

Reward basis total

275,732,443,050

epoch 3,734 · 13 devices positive basis

Epoch alignment

Aligned

payout 3,734 · contribution 3,734

Eligible devices

must heartbeat in epoch 3,733

Phone Earnings AllocationExact on-chain per-device reward basis, allocated by each device's share of that reward basis.

5EMsBLso...MhGZFc block #3,360,649

Aligned allocation

Uses the exact retained farm payout and exact on-chain per-device reward-basis share from the same epoch. Devices are only included if they had a retained processor heartbeat in the previous epoch and have positive reward basis.

exact share basis

50 rows 100 rows 250 rows


5Gq7g7Rehx...5np9RgJKUnknown deviceAndroid	down+10% boost · 55,156 → 60,672	46,968,290,433121	17.0340%	0.008326 ACU	3,734	17 hrs agoJun 23, 2026, 1:56 PM UTC

5Gq7g7Rehx...5np9RgJKUnknown deviceAndroid

0.008326 ACUdown+10% · 55,156→60,672

Reward basis46,968,290,433

Basis share17.0340%

Epoch3,734

Heartbeat17 hrs ago

Showing 1-1

Excluded Devices12

These devices are managed by the farm but were excluded from derived payout because they did not satisfy the previous-epoch heartbeat rule or had zero reward basis.

Device	Reason	Reward Basis	Prev Epoch Heartbeat
5GefyGw37m...fovDzJ1NAndroid	No previous-epoch heartbeat	50,576,587,702	No
5D1K8suFd7...nvrrEku4Android	No previous-epoch heartbeat	18,248,479,340	No
5DhtDAhKnx...48HpKpX7Android	No previous-epoch heartbeat	18,108,180,902	No
5FpnCnBWKj...o4eGB7dFAndroid	No previous-epoch heartbeat	17,652,390,702	No
5HTDbb8zCm...f3QjhBfqAndroid	No previous-epoch heartbeat	17,622,342,844	No
5HEPqsofZt...5mrA9mmxAndroid	No previous-epoch heartbeat	17,447,821,753	No
5ECm5GJ7oU...ZGajqZA9Android	No previous-epoch heartbeat	16,756,610,580	No
5DJWn1zUEJ...pH9NnHEVAndroid	No previous-epoch heartbeat	15,813,325,575	No
5F6N54n2Bs...xoae2s2RAndroid	No previous-epoch heartbeat	14,872,723,330	No
5GceZy2Sp4...PPnUmTxTAndroid	No previous-epoch heartbeat	14,795,532,363	No
5D5BkDG155...x3moVQiJAndroid	No previous-epoch heartbeat	13,529,695,067	No
5GCrsNsfYY...JqJC2tHSAndroid	No previous-epoch heartbeat	13,340,462,459	No

How This Page WorksFAQ

What is exact?

Farm payout is exact from the retained manager reward transfer. Device reward basis is exact from the live on-chain processor rewardContribution field, and is shown here in raw basis units rather than ACU.

What is derived?

Derived device payout is calculated by allocating the exact farm payout across devices using each device's exact reward-basis share.

Formula

Device basis share = device reward basis / total farm reward basis.

Derived device payout = exact farm payout × device basis share.

derived_payout = farm_payout * (device_basis / farm_basis_total)

For epoch 3,734 on this page: derived_payout = 0.048883 * (device_basis / 275,732,443,050)

When is it strongest?

When payout epoch and reward-basis epoch match. That means the device share basis and the farm payout belong to the same epoch.

Who is eligible?

A device must have a retained processor heartbeat in the previous epoch and a positive reward basis to appear in the payout table.

Why can this differ from canonical phone payout?

The chain exposes exact processor reward basis and exact farm payout, but not a long historical canonical per-phone payout ledger. This page shows the best aligned allocation model from those exact inputs.