For ten and a half hours, this address kept rebuilding multi-step vault routes. Its 85 transactions produced 60 exact call sequences; 54 failed, and 49 stopped at the same vault deposit guard. The activity resembles repeated route experimentation or automated execution, but the evidence does not identify an operator or prove a completed exchange.
The complete frozen-window history runs from 13:03:44 to 23:31:25 UTC on 2026-07-19. The detailed stream is capped at the latest 500 transactions, but it returns all 85 transactions here, so the two scopes coincide.
Rhythm and repertoire
The cadence was intermittent rather than continuous: the mean gap was 7 minutes 28 seconds, the median 4 minutes 56 seconds, and the 90th-percentile gap 17 minutes 7 seconds. The longest idle period was about 35 minutes 45 seconds. The busiest minute contained three transactions, and the longest consecutive failure run was seven.
Only 24 of 85 transactions asserted the behavior execute-swap-route. Those rows covered 19 route variants and included vault withdrawals, adapter conversions, router or pool calls, and thresholded deposits. The other 61 transactions withheld a behavior claim, although their call compositions still show linked multi-step attempts. Across the entire stream, 24 transactions received a complete structural explanation, 36 were only partly explained, and 25 were described at the call-group level. A complete explanation is not the same as a successful execution.
The shared pattern is a custody round trip: withdraw value from a vault, pass it through several conversion or routing steps, then present the result for deposit. In the representative route H7un4tMb, the address withdrew value, created supporting coins, reached DeepBook and a router, and returned a SUI balance toward the vault. It submitted 50 SUI and guarded on 50 SUI as a minimum output; those guards do not prove that 50 SUI was spent or received, and the record does not establish an exchange.
Where the attempts stopped
Failures dominate the history: 54 of 85 transactions carried an execution error. Forty-nine stopped at vault::deposit_with_threshold_and_event; five had no recorded abort site. Since Sui rolls back application effects after an abort, reaching earlier swap or adapter calls proves an attempt, not a lasting custody change.
AUhrMeq shows the pattern clearly. It withdrew value, passed it through several conversion steps, reached an adapter call, and then aborted at the deposit step with a Move abort. It submitted 5 SUI and guarded on 5 SUI, but the application changes were rolled back. The sender-level movement recorded for the transaction was only a 425,660-MIST SUI gas charge.
The latest transaction, 4TRvV2wv, shows the unresolved edge of the repertoire. It submitted 10 USDC and guarded on 10 USDC, then reached an unsupported v2::swap_x_to_y call before continuing to a deposit step. It did not carry an execution error, but the evidence still does not establish an exchange or the resulting custody state.
What moved
The sender paid 87,761,288 MIST of SUI gas across the 85 transactions, or 0.087761288 SUI. The separate holding accounting shows 0.004546746 SUI in, 0.082353832 SUI out, and a net holding change of −0.077807086 SUI. These figures must not be added together: the same gas charge can also appear in the holding accounting.
One transaction recorded a holding inflow of 25,314 raw USDC, displayed as 0.025314 USDC. There are no prices or proven exchange outcomes, so these movements do not establish profit, loss, or a trade result. All 85 transactions list this address as their gas owner; none were sponsored.
The largest single gas charge was 8,963,208 MIST in DTw1m1iq. That transaction remained only partly explained and carried no asserted behavior, another sign that complex routing and semantic certainty are separate things.
This dossier describes one sender identity inside one frozen Sui window. It does not establish a person, company, bot, operator, strategy, or profitability.
Useful exits are H7un4tMb, the approved route pattern sui/execute-swap-route/strict-remap-next-b3bb37268345/v1, the repeated vault package 0xf0b2cc8ccb3addcef3696c5f11ea44518f09b4e8ab4d86abd25f343cbcc9d5c6, and the unresolved route in 4TRvV2wv.