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

#35600·5CvBAGTW...zTit99·Phone Earnings

Staking

Farm payout

0.013446 ACU

epoch 4,419 · 11d ago

Reward basis total

894,963,414,638

epoch 4,419 · 35 devices positive basis

Epoch alignment

Aligned

payout 4,419 · contribution 4,419

Eligible devices

must heartbeat in epoch 4,418

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

5CvBAGTW...zTit99 block #3,977,230

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


5DRqsDYhph...unpGQdr5Unknown device	unknown	14,180,407,052version unknown	1.5844%	0.000213 ACU	4,419	—

5DRqsDYhph...unpGQdr5Unknown device

0.000213 ACUunknown

Reward basis14,180,407,052

Basis share1.5844%

Epoch4,419

Heartbeat—

Showing 1-1

Excluded Devices34

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
5EbCxHDXEm...HG3VKgKTUnknown device	No previous-epoch heartbeat	37,764,737,061	No
5FvHdriZv2...MzJJQJozUnknown device	No previous-epoch heartbeat	36,767,925,399	No
5Hk26B8Lnp...XgiX1uNQUnknown device	No previous-epoch heartbeat	36,589,064,597	No
5FHyrzuuzB...N4DwCh2PUnknown device	No previous-epoch heartbeat	36,532,365,711	No
5EEv1PtBCB...kyW5xw7DUnknown device	No previous-epoch heartbeat	35,830,541,966	No
5C6HLra797...HLSgyNsJUnknown device	No previous-epoch heartbeat	34,867,998,453	No
5FQsGfCTeT...HkyrYMvdUnknown device	No previous-epoch heartbeat	34,726,332,770	No
5H5qyyWCvh...2QShmWbNUnknown device	No previous-epoch heartbeat	34,648,462,329	No
5DY7BP1RTX...mTgueVRAUnknown device	No previous-epoch heartbeat	34,599,305,162	No
5D3XpWxauC...JpLKapAbUnknown device	No previous-epoch heartbeat	34,589,714,425	No
5CzqWJcTf8...UbpjCqqyUnknown device	No previous-epoch heartbeat	34,555,509,960	No
5DbBCkf77H...1FtcvRbzUnknown device	No previous-epoch heartbeat	34,368,145,886	No
5DbcBUMKua...GTJ8L86eUnknown device	No previous-epoch heartbeat	34,133,710,063	No
5F8cspkdX8...EXZvEw3XUnknown device	No previous-epoch heartbeat	32,973,924,108	No
5HhPHqtAvq...2nNwYzNvUnknown device	No previous-epoch heartbeat	31,999,293,078	No
5Dh5ipnLBX...NtYqfegLUnknown device	No previous-epoch heartbeat	31,770,261,601	No
5CGo4wk8GN...VvAMBmC6Unknown device	No previous-epoch heartbeat	30,956,202,799	No
5Cgd61Ta2W...FP52a1Q6Unknown device	No previous-epoch heartbeat	30,781,557,484	No
5EzV9xriWv...uSgMCo7AUnknown device	No previous-epoch heartbeat	29,027,560,042	No
5H3EXdAzY7...ecV4hNr5Unknown device	No previous-epoch heartbeat	20,660,404,693	No
5GEV2wREbT...T8aF5g2pUnknown device	No previous-epoch heartbeat	20,483,549,350	No
5HLBdnXnhy...K7kQAGmRUnknown device	No previous-epoch heartbeat	20,128,512,469	No
5CASzFeXtE...69hvjZggUnknown device	No previous-epoch heartbeat	16,504,673,729	No
5CvGTWoFDe...k1PkjHu2Unknown device	No previous-epoch heartbeat	14,834,932,652	No
5D6ZSDWovb...74rkST6SUnknown device	No previous-epoch heartbeat	14,372,877,503	No
5EACuuVivV...y2cZperwUnknown device	No previous-epoch heartbeat	14,329,416,014	No
5Cw6uFMPaa...3DqgPCjrUnknown device	No previous-epoch heartbeat	14,289,125,674	No
5E2Pz9uZy7...dfPXtZK7Unknown device	No previous-epoch heartbeat	14,266,214,529	No
5CUGa6TZ8E...Ysytj3mrUnknown device	No previous-epoch heartbeat	14,145,936,384	No
5DZPKqpFcF...dn1xUEKuUnknown device	No previous-epoch heartbeat	14,028,450,037	No
5F5fnsHipC...TpoQeQHBUnknown device	No previous-epoch heartbeat	13,984,556,193	No
5FBLXZkchj...SkS7pnSoUnknown device	No previous-epoch heartbeat	13,909,806,859	No
5GpvCVrRxP...sD4QE1cPUnknown device	No previous-epoch heartbeat	13,831,075,302	No
5DQNpPzFcu...P5PCgCECUnknown device	No previous-epoch heartbeat	13,530,863,304	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 4,419 on this page: derived_payout = 0.013446 * (device_basis / 894,963,414,638)

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.