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 #4251 | Acurast Pulse

#4251·5GqPwM2h...ZEmGnW·Phone Earnings

Staking

Farm payout

0.014917 ACU

epoch 2,973 · 50d ago

Boost benefit

+0.000608 ACU

· network 58.8%

0 of 0 devices · +0 compute

Reward basis total

635,195,850,734

epoch 2,973 · 36 devices positive basis

Epoch alignment

Aligned

payout 2,973 · contribution 2,973

Eligible devices

must heartbeat in epoch 2,972

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

5GqPwM2h...ZEmGnW block #2,675,750

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

No managed devices with current contribution state were available for this phone farm.

Showing 0-0

Excluded Devices37

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
5DjqUPxUPJ...f1k7EVSkUnknown device	No previous-epoch heartbeat	30,344,705,030	No
5CHaQwPk7o...69Cq5tSMUnknown device	No previous-epoch heartbeat	29,668,615,807	No
5GFKz9mrDo...QYY5vxwnUnknown device	No previous-epoch heartbeat	27,020,731,139	No
5CfmepcaCW...L6bi3B4VUnknown device	No previous-epoch heartbeat	26,730,461,233	No
5CXrL1pwJ7...YLUTjRCsUnknown device	No previous-epoch heartbeat	25,992,604,765	No
5Gjo1XmuNL...3zJ5bsfkUnknown device	No previous-epoch heartbeat	21,158,273,171	No
5Hk5NPHjLj...66DM5zW2Unknown device	No previous-epoch heartbeat	21,072,476,255	No
5EP7fd84dC...UV8TT7nVUnknown device	No previous-epoch heartbeat	21,011,731,753	No
5GoSzuVtXa...ssGXm2oLUnknown device	No previous-epoch heartbeat	20,865,127,115	No
5GqNkossNQ...GK8vtx1ZUnknown device	No previous-epoch heartbeat	20,835,685,806	No
5G6ctmupEY...UrbjdiRfUnknown device	No previous-epoch heartbeat	20,798,866,413	No
5FEjttNUaz...AY9QVpCMUnknown device	No previous-epoch heartbeat	20,639,362,414	No
5H7DbdfprZ...nT2pbt1NUnknown device	No previous-epoch heartbeat	19,180,016,201	No
5G6GywpBGb...PURHRFFSUnknown device	No previous-epoch heartbeat	18,646,904,112	No
5H9HWCj8tR...gprabcPPUnknown device	No previous-epoch heartbeat	18,132,651,571	No
5GpvTq2Ukm...FZx1cdGdUnknown device	No previous-epoch heartbeat	17,190,936,299	No
5EKGHNFmQS...XJC6MhHGUnknown device	No previous-epoch heartbeat	16,982,902,161	No
5GWvtyhZH3...fHd7Z4dRUnknown device	No previous-epoch heartbeat	16,450,757,362	No
5H18CWg6MS...v6AoeSyyUnknown device	No previous-epoch heartbeat	15,869,327,856	No
5D1Nn54grN...xMVbEcx1Unknown device	No previous-epoch heartbeat	15,841,561,772	No
5GLkYWqYBg...WyqaVj5zUnknown device	No previous-epoch heartbeat	15,014,653,371	No
5DX2dkhTyo...R2DDzmFZUnknown device	No previous-epoch heartbeat	14,702,113,050	No
5GDikidR3B...fU5d7oRWUnknown device	No previous-epoch heartbeat	14,453,740,312	No
5Df86twAyk...9DyzsS6TUnknown device	No previous-epoch heartbeat	14,359,190,380	No
5HNqDctGaE...2rucWtECUnknown device	No previous-epoch heartbeat	13,858,891,074	No
5GpzPzBU5h...i3n7ciWjUnknown device	No previous-epoch heartbeat	13,534,244,182	No
5DA9sT6vsR...cubHyVqkUnknown device	No previous-epoch heartbeat	13,507,016,794	No
5G6d5Lv4Zc...E9JCXBN2Unknown device	No previous-epoch heartbeat	13,444,800,002	No
5GyuYBaaBy...tabGxtsCUnknown device	No previous-epoch heartbeat	13,251,099,090	No
5E5ETUCudU...UZDJzddjUnknown device	No previous-epoch heartbeat	12,852,458,625	No
5Eakp8Cci5...f6q2SiKYUnknown device	No previous-epoch heartbeat	12,763,754,944	No
5EFHYmqyup...LkT4xUsaUnknown device	No previous-epoch heartbeat	12,619,058,445	No
5Hj3Nx3PRr...YYrsYWryUnknown device	No previous-epoch heartbeat	12,447,631,492	No
5FpsrsNCRE...P3hKN9iuUnknown device	No previous-epoch heartbeat	11,863,437,258	No
5EifqAR4jv...rtD1bF5dUnknown device	No previous-epoch heartbeat	11,472,420,628	No
5GNnDPxkHk...Avm69bGGUnknown device	No previous-epoch heartbeat	10,617,642,852	No
5FkACgXA85...gy99fXMgUnknown device	No previous-epoch heartbeat	0	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 2,973 on this page: derived_payout = 0.014917 * (device_basis / 635,195,850,734)

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.