For 635 minutes on July 19, this address did almost one thing: it submitted configured inventory strategies. Across the complete frozen-window history, 1,237 of 1,494 transactions carried the asserted behavior execute-configured-strategy; 57 failed at the same early guard. The bursty cadence is consistent with scheduled or programmatic execution, but the record does not establish who controls the address.
The rhythm
The whole-history stream runs from 13:02:16 to 23:37:21 UTC. Its median gap is 0 milliseconds, meaning many submissions arrived in tight bursts; the mean gap was 25.5 seconds and the 90th-percentile gap 37.0 seconds. The longest idle period was about 26 minutes 19 seconds. The busiest minute was 17:01 UTC, with 168 transactions, and the longest uninterrupted run without a recorded failure was 189 transactions.
The detailed stream is deliberately capped at the latest 500 transactions, from 19:54:29 to 23:37:21 UTC. There, the median gap was 226 milliseconds and the mean was 26.8 seconds. It contained 12 distinct transaction shapes: one declared strategy, repeated through several recipes, plus 84 transactions whose connected calls did not establish a complete purpose.
One behavior, eight recipes
The declared behavior appears in 1,237 of the 1,494 whole-history transactions. The largest variants were:
- direction-scheduled inventory strategy: 521 transactions;
- balanced-and-scheduled strategy: 272;
- excess-inventory strategy: 143;
- four-coordinator inventory sequence: 115;
- four other configured variants: 186 combined.
The latest-500 stream preserves that shape: 416 transactions carried an asserted strategy explanation, while 84 showed an authorization check followed by strategy execution without enough evidence to name the whole purpose.
The analyzed strategy package describes managed balances, directional schedules, price limits, balance floors, and a linked-pool flash-swap-and-repay path when a tranche is viable. A completed coordinator call identifies the scheduled inventory routine; it does not prove that a flash swap occurred, that an exchange took place, or that the sender received an asset.
The repeated failure
All 57 whole-history failures stopped at the same first-call guard, accounting for 3.8% of the 1,494 transactions. The failed attempts consumed 406,021,980 MIST, or 0.406021980 SUI, in gas. The latest-500 stream contains 37 such failures, all at that same guard, consuming 200,864,768 MIST.
In 753B4wLe, at 23:21:44 UTC, the transaction attempted the guard and aborted with Move code 200. The analyzed guard associates that code with a proposed sequence value below the stored counter. The later two submitted strategy steps did not run, and application changes from the aborted transaction were rolled back. This is a repeated boundary condition, not evidence that the strategy itself completed and failed economically.
What actually moved
Across the complete history, the only sender-boundary movement recorded is SUI gas out: 15,604,325,144 MIST, or 15.604325144 SUI, across all 1,494 transactions. The sender and gas owner are the same address on every transaction, so none of this activity was sponsored. SUI is the native asset used for gas on Sui. [Sui documentation](https://docs.sui.io/paper/sui.pdf)
The latest 500 transactions account for 4.329827068 SUI of that gas. No application asset movement is attributed to the sender in either scope. That does not prove that the managed strategy moved nothing internally; it only bounds what the stored evidence assigns to this address. There are no prices here, so the record cannot establish profit or loss.
Three useful close-ups
4tr5JsDh is the latest observed transaction, at 23:37:21 UTC. It ran the authorization check followed by the direction-scheduled strategy and paid 3,651,204 MIST in gas. Its explanation describes the coordinator, not a particular exchange result.
753B4wLe is the clean failure contrast: the same guard stopped the transaction before the strategy call, with later effects rolled back.
ABTwQm8c, at 23:07:08 UTC, ran the same broad two-step shape but received no asserted whole-transaction purpose. It is a useful reminder that recognizable calls do not automatically establish intent.
The next trails are the direction-scheduled pattern sui/execute-configured-strategy/cs-83d07f9b27ff/v1, the balanced-and-scheduled pattern sui/execute-configured-strategy/cs-1406e4de7a13/v1, the sequence guard at 0xc72126…4a5c50, and the strategy package at 0x496ee3…b46bc5.