1,210 reward-pool attempts, 1,210 failures, and not one committed payout

For 10 hours and 35 minutes on July 19, this address did one thing: it attempted to distribute rewards from a shared pool. All 1,210 attempts failed at pool::distribute_rewards, arriving roughly every 31.5 seconds. The rhythm is consistent with automated retrying, but the chain does not establish who controlled the address or why it kept retrying.

A perfectly stable failure loop

The complete history runs from 13:02:01.789 UTC to 23:37:37.186 UTC. Every transaction used the same asserted operation, the same pattern, and the same package revision. The median gap was 31,497 milliseconds; 90% of gaps were no wider than 31,733 milliseconds, and the longest idle period was 39,110 milliseconds. The single uninterrupted failure run lasted all 1,210 transactions.

The detailed ledger is a separate, capped view of the latest 500 explained transactions, beginning at 19:15:12.698 UTC. Those 500 rows repeat the same command, abort site, gas amount, and sender movement. The first inspected row, B76MhMYE, a middle row, 31P7yJLh, and the final row, 39Zogpk4, all show a MoveAbort with code 1 at the same distribution function.

The reader explanation is unusually direct: “it attempted a distribution step but aborted at that step.” The package analysis identifies the observed branch as an empty-escrow check. The aggregate record proves the common abort site for all 1,210 attempts; it does not expose a separate branch label for every individual row.

What the money says

Across the complete history, the sender has one proven asset movement: SUI leaving in the gas category, totaling 156,312,640 MIST, or 0.15631264 SUI. A matching 156,312,640-MIST SUI change also appears as a holding delta. These are separate evidence categories and must not be added together.

The latest-500 ledger shows the same pattern at smaller scope: 64,592,000 MIST in each category. Each inspected transaction records a boundary change of −0.000129184 SUI. Because the distribution call aborted atomically, application changes were rolled back; these records establish attempted reward distribution, not a completed payout. No reward inflow or committed application transfer is proven for this sender.

The same address paid its own gas in all 1,210 transactions. That describes the transaction arrangement, not the identity of a person, company, operator, or bot.

The useful exits

• Transaction: B76MhMYE shows the first detailed attempt in the latest-500 stream.
• Transaction: 39Zogpk4 shows the final attempt in the complete history.
• Pattern: sui/execute-pool-distribute-rewards/roster-f0033/v1.
• Package revision: 0x175918d5654f0eaf645412ce72399bef2c2508e95f01bd81bf27c880b839e1b8.