Within the frozen Sui window, 0x7777e52f1cf736465008c8bc6190b8e3e585ec257670b82245adabf506817777 repeatedly did two things: it ran guarded swap routes and invoked a configured strategy. The complete-history record contains 1,311 transactions, 201 failures, and 1,309 sponsored executions. The activity resembles automated treasury or trading infrastructure, but the evidence does not establish a person, company, operator, or bot behind the address.
The rhythm
The complete-history record runs from 13:02:01 to 23:21:58 UTC. Its median gap is 0 milliseconds because transactions arrive in dense bursts; the 90th-percentile gap is about 10.2 seconds, and the longest idle period is about 45.6 minutes. The busiest minute was 17:01 UTC, with 230 transactions, and the longest uninterrupted run of successful executions was 52.
The latest-500 stream covers a different scope: 18:15:50 to 23:21:58 UTC. Its median gap is 216 milliseconds, with 107 transactions in the busiest minute at 22:15 UTC. That sub-second burst cadence is consistent with scheduled or automated execution, but it does not identify who—or what—operated the address.
Sponsorship is unusually clear. Across the complete history, five gas owners appear, but the sender itself paid for only two transactions; 1,065 were paid by the gas owner ending …550000, 182 by …1abeef, and 60 by …63c0de. Every one of the latest 500 transactions was sponsored.
The repertoire
Of the 1,311 complete-history transactions, 316 were identified as execute-swap-route and 172 as execute-configured-strategy. The other 823 were described only as connected call sequences, partial explanations, or transactions without a recognized end-to-end behavior.
The route group was not one uniform call. It included 108 uses of strict-remap-a32d9ca9f95c/v1, 64 of strict-remap-next-1d6e44360e03/v1, and several treasury-mediated variants. Their authored explanations describe withdrawals from treasury custody, calls into routers or exchange-related components, and thresholded deposits of the returned asset. They establish a route-shaped workflow, not an exchange result.
The strategy group used 5a6335-bt/v1 172 times. Its explanation says the entrypoint selects a stateful path involving configuration, pricing, treasury, rewards, and balances. The retained evidence does not reveal which conditional work occurred inside each call, so even a successful execution does not establish an internal trade.
The latest-500 stream contains 109 swap-route labels, 87 configured-strategy labels, and 304 transactions without a named behavior. This capped stream therefore preserves the same two-mode character seen across the complete history.
Where executions stopped
Failures are concentrated at the treasury return boundary. In the complete history, 158 of 201 failures—78.6%—stopped at treasury::deposit_coin_with_threshold_and_event. Another 17 stopped at the corresponding balance-deposit function. Ten stopped during a simulated sell, six during a simulated buy, two at price validation, one in a cfx::op call, and seven have no recorded abort site.
The latest-500 stream shows the same shape: 62 failures at the coin-deposit threshold, nine at the balance-deposit threshold, six during simulated buys, and one with an unrecorded site.
CdH31RZG is a useful example. It withdrew a USDC coin, passed it through a router touching SUI and USDC, and attempted to deposit the returned SUI. The transaction submitted 66.974923 USDC and guarded on a minimum output of 89.479916608 SUI, then aborted at the treasury deposit call. The application effects rolled back, so this proves an attempted route—not a completed exchange or deposit.
The money boundary
The complete-history movement report contains only two movement-bearing transactions. Both show 2,568,616 MIST of SUI moving out: once in the gas record and once in the holding record. Those are two evidence views of the same amount and must not be added together. No sender-bound cross-asset receipt or profit can be established from this record.
The transactions associated with the address carry 14,859,269,112 MIST in net-gas records, but that is not a bill attributable to the sender: almost all executions were sponsored. The largest recorded gas figure appears on AZwnEXHb, where a route submitted 0.09 wBTC toward a Momentum conversion touching LBTC and wBTC, then stopped because the gas budget was too small. The submitted amount is not evidence that the value was spent or that an output was received.
What to inspect next
CUSgbe7x shows a successful vectorized route whose evidence still does not establish an exchange. 4Q5Pj5xK shows the configured-strategy path and its deliberately unresolved conditional work. CdH31RZG shows the dominant failure boundary. The final transaction, HgGgCAUV, was another sponsored multi-step composition without a named end-to-end behavior.
The address is best read as a high-burst, heavily sponsored execution identity with a stable two-part repertoire and a recurring treasury-deposit failure boundary. Nothing in this frozen window establishes its operator or whether any route was economically favorable.