Phone Farm

Loading fleet overview

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

Loading page data…

Acurast Pulse

Loading live view

Loading the latest available information.

Loading page data…

Manager Phone Earnings #119 | Acurast Pulse

Phone earnings

Manager #119 · Latest completed epoch 5597

Heartbeat history ↗

Farm payout: 0.439817 ACU
Heartbeat fees: —
After heartbeat fees: —
Included in payout: 13 / 16

#119·Manager 119·Phone Earnings

Staking

Showing the last completed payout epoch 5597. View older epochs in the heartbeat calculator.

Payout epoch 5597 uses reward basis from epoch 5596. Heartbeat fees cover payout epoch 5597. 13 of 16 current devices were included; the remaining 3 have no payout share because they were not present in that historical reward-contribution snapshot. Device status and last heartbeat are current.

Reward basis total

450,363,245,584

epoch 5,596 · 13 devices positive basis

Epoch alignment

Matched

payout 5,597 · contribution 5,596

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

Historical payout allocation

Uses the retained completed farm payout and the historical reward-basis shares that produced it. Per-phone payouts are derived allocations, not individual on-chain transfers.

matched share basis

HB fees are matched to payout epoch 5597. Missing fee breakdowns stay unknown. Derived net is shown only when the payout and its corresponding reward basis are verified; it excludes marketplace fees, electricity and hardware costs.

Heartbeat counts cover payout epoch 5597. “Without metrics” means an empty metrics payload, not proof of a deployment. Unclassified payloads count toward the total only. A dash means the breakdown is unavailable or still backfilling.

Find a phonePhone modelSort all phones

13 matching of 13 eligible phones · Showing 1–13. Sorting applies to all matching phones, before pagination.

Loading phone models: 0/16. Earnings and fleet-wide sorting are available.


5Ew6adVzVD...Bjv9Shf5Unknown deviceAndroid	active	58,785,604,349140	13.0529%	0.057409 ACU	—	—	—	—	—	5,596	Oct 23, 2026, 4:48 PM UTCOct 23, 2026, 4:48 PM UTC
5D4gCxKkxm...aybqP6goUnknown deviceAndroid	active	57,570,525,932140	12.7831%	0.056222 ACU	—	—	—	—	—	5,596	Oct 23, 2026, 5:11 PM UTCOct 23, 2026, 5:11 PM UTC
5HTK8Sg675...Lg3D5YBVUnknown deviceAndroid	active	48,848,881,637140	10.8465%	0.047705 ACU	—	—	—	—	—	5,596	Oct 23, 2026, 5:10 PM UTCOct 23, 2026, 5:10 PM UTC
5G3zBt3MUL...6bHivxFxUnknown deviceAndroid	active	48,016,246,424140	10.6616%	0.046891 ACU	—	—	—	—	—	5,596	Oct 23, 2026, 5:04 PM UTCOct 23, 2026, 5:04 PM UTC
5CGepyoCzD...mWwaGR4fUnknown deviceAndroid	active	43,667,586,938140	9.6960%	0.042645 ACU	—	—	—	—	—	5,596	Oct 23, 2026, 5:09 PM UTCOct 23, 2026, 5:09 PM UTC
5DssJyKHrL...aydsoQZcUnknown deviceAndroid	active	39,451,567,420140	8.7599%	0.038527 ACU	—	—	—	—	—	5,596	Oct 23, 2026, 4:49 PM UTCOct 23, 2026, 4:49 PM UTC
5EBCKoegAS...KWMESPTbUnknown deviceAndroid	active	30,400,781,756140	6.7502%	0.029688 ACU	—	—	—	—	—	5,596	Oct 23, 2026, 5:10 PM UTCOct 23, 2026, 5:10 PM UTC
5FvSUKqEia...jezxZJ22Unknown deviceAndroid	active	29,483,975,264140	6.5467%	0.028793 ACU	—	—	—	—	—	5,596	Oct 23, 2026, 5:12 PM UTCOct 23, 2026, 5:12 PM UTC
5E67onEtuP...MnKjTigoUnknown deviceAndroid	active	24,102,724,092140	5.3518%	0.023538 ACU	—	—	—	—	—	5,596	Oct 23, 2026, 5:00 PM UTCOct 23, 2026, 5:00 PM UTC
5DPHdmieSQ...ATFp7hjYUnknown deviceAndroid	active	21,715,309,391140	4.8217%	0.021206 ACU	—	—	—	—	—	5,596	Oct 23, 2026, 5:09 PM UTCOct 23, 2026, 5:09 PM UTC
5HBGFUXMBy...Hdf53GT4Unknown deviceAndroid	active	21,212,427,744140	4.7100%	0.020715 ACU	—	—	—	—	—	5,596	Oct 23, 2026, 5:09 PM UTCOct 23, 2026, 5:09 PM UTC
5GW8sRLiJr...xkUZqpyrUnknown deviceiOS	active	15,488,021,10663381	3.4390%	0.015125 ACU	—	—	—	—	—	5,596	Oct 23, 2026, 4:49 PM UTCOct 23, 2026, 4:49 PM UTC
5GD57xKoKb...e4pPsH36Unknown deviceAndroid	active	11,619,593,531140	2.5800%	0.011347 ACU	—	—	—	—	—	5,596	Oct 23, 2026, 5:06 PM UTCOct 23, 2026, 5:06 PM UTC

5Ew6adVzVD...Bjv9Shf5Unknown deviceAndroid

0.057409 ACUactive

# Heartbeats—

With metrics—

Without metrics—

HB fees · payout epoch 5597—

Derived after HB fees—

Reward basis58,785,604,349

Basis share13.0529%

Basis epoch5,596

HeartbeatOct 23, 2026, 4:48 PM UTC

5D4gCxKkxm...aybqP6goUnknown deviceAndroid

0.056222 ACUactive

# Heartbeats—

With metrics—

Without metrics—

HB fees · payout epoch 5597—

Derived after HB fees—

Reward basis57,570,525,932

Basis share12.7831%

Basis epoch5,596

HeartbeatOct 23, 2026, 5:11 PM UTC

5HTK8Sg675...Lg3D5YBVUnknown deviceAndroid

0.047705 ACUactive

# Heartbeats—

With metrics—

Without metrics—

HB fees · payout epoch 5597—

Derived after HB fees—

Reward basis48,848,881,637

Basis share10.8465%

Basis epoch5,596

HeartbeatOct 23, 2026, 5:10 PM UTC

5G3zBt3MUL...6bHivxFxUnknown deviceAndroid

0.046891 ACUactive

# Heartbeats—

With metrics—

Without metrics—

HB fees · payout epoch 5597—

Derived after HB fees—

Reward basis48,016,246,424

Basis share10.6616%

Basis epoch5,596

HeartbeatOct 23, 2026, 5:04 PM UTC

5CGepyoCzD...mWwaGR4fUnknown deviceAndroid

0.042645 ACUactive

# Heartbeats—

With metrics—

Without metrics—

HB fees · payout epoch 5597—

Derived after HB fees—

Reward basis43,667,586,938

Basis share9.6960%

Basis epoch5,596

HeartbeatOct 23, 2026, 5:09 PM UTC

5DssJyKHrL...aydsoQZcUnknown deviceAndroid

0.038527 ACUactive

# Heartbeats—

With metrics—

Without metrics—

HB fees · payout epoch 5597—

Derived after HB fees—

Reward basis39,451,567,420

Basis share8.7599%

Basis epoch5,596

HeartbeatOct 23, 2026, 4:49 PM UTC

5EBCKoegAS...KWMESPTbUnknown deviceAndroid

0.029688 ACUactive

# Heartbeats—

With metrics—

Without metrics—

HB fees · payout epoch 5597—

Derived after HB fees—

Reward basis30,400,781,756

Basis share6.7502%

Basis epoch5,596

HeartbeatOct 23, 2026, 5:10 PM UTC

5FvSUKqEia...jezxZJ22Unknown deviceAndroid

0.028793 ACUactive

# Heartbeats—

With metrics—

Without metrics—

HB fees · payout epoch 5597—

Derived after HB fees—

Reward basis29,483,975,264

Basis share6.5467%

Basis epoch5,596

HeartbeatOct 23, 2026, 5:12 PM UTC

5E67onEtuP...MnKjTigoUnknown deviceAndroid

0.023538 ACUactive

# Heartbeats—

With metrics—

Without metrics—

HB fees · payout epoch 5597—

Derived after HB fees—

Reward basis24,102,724,092

Basis share5.3518%

Basis epoch5,596

HeartbeatOct 23, 2026, 5:00 PM UTC

5DPHdmieSQ...ATFp7hjYUnknown deviceAndroid

0.021206 ACUactive

# Heartbeats—

With metrics—

Without metrics—

HB fees · payout epoch 5597—

Derived after HB fees—

Reward basis21,715,309,391

Basis share4.8217%

Basis epoch5,596

HeartbeatOct 23, 2026, 5:09 PM UTC

5HBGFUXMBy...Hdf53GT4Unknown deviceAndroid

0.020715 ACUactive

# Heartbeats—

With metrics—

Without metrics—

HB fees · payout epoch 5597—

Derived after HB fees—

Reward basis21,212,427,744

Basis share4.7100%

Basis epoch5,596

HeartbeatOct 23, 2026, 5:09 PM UTC

5GW8sRLiJr...xkUZqpyrUnknown deviceiOS

0.015125 ACUactive

# Heartbeats—

With metrics—

Without metrics—

HB fees · payout epoch 5597—

Derived after HB fees—

Reward basis15,488,021,106

Basis share3.4390%

Basis epoch5,596

HeartbeatOct 23, 2026, 4:49 PM UTC

5GD57xKoKb...e4pPsH36Unknown deviceAndroid

0.011347 ACUactive

# Heartbeats—

With metrics—

Without metrics—

HB fees · payout epoch 5597—

Derived after HB fees—

Reward basis11,619,593,531

Basis share2.5800%

Basis epoch5,596

HeartbeatOct 23, 2026, 5:06 PM UTC

Devices without payout share3

These current fleet devices received no share of this completed payout. A device can be absent from the historical reward-contribution snapshot, or have a recorded zero reward basis.

Device	Why no payout share	Reward Basis
5CcQve3ZX7...ain2u4QCUnknown device	Not included in reward-contribution snapshot for epoch 5596	0
5FgC6cnhwd...CSL7mY6UUnknown device	Not included in reward-contribution snapshot for epoch 5596	0
5GKTMyzfWN...vrue2WwYUnknown device	Not included in reward-contribution snapshot for epoch 5596	0

How This Page WorksFAQ

What is exact?

Farm payout is exact from the retained manager reward transfer. Device reward basis comes from the retained historical snapshot for a completed epoch, or the on-chain processor rewardContribution field for a live allocation. It is shown 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 5,597 on this page: derived_payout = 0.439817 * (device_basis / 450,363,245,584)

When is it strongest?

When the completed payout is linked to its retained reward basis from the preceding epoch, and heartbeat fees for the payout epoch are verified.

Who is eligible?

A device must have positive reward basis in the retained historical snapshot. Phones without retained basis are not assigned an invented payout.

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.