For just over ten hours in the frozen corpus, this address repeatedly assembled complex swap-like transactions, but the evidence rarely resolved what the complete transaction was meant to accomplish. It sent 260 eligible transactions between 13:02:14 and 23:27:27 UTC. Only 19 received an asserted route-purpose explanation; the other 241 were described only by their call structure or remained unexplained. The repetition is consistent with programmatic execution, but the address alone does not establish a person, operator, or bot.
A stop-and-start route builder
The whole-history rhythm is deliberate-looking without being metronomic: the median gap was 66.9 seconds, the mean was 144.8 seconds, and the 90th-percentile gap was 342.3 seconds. The longest idle period was 27 minutes 41 seconds, while the busiest minute contained only three transactions. The longest uninterrupted run without an execution error was 28 transactions.
The detailed stream is capped at the latest 500 classifiable transactions. This address has only 260 such rows in the frozen corpus, so the ledger and detail stream cover all 260 transactions rather than a truncated sample.
One recognized repertoire, many unresolved shapes
The 19 recognized route transactions used five exact variants: 8, 4, 3, 3, and 1 occurrence. Their authored explanations describe router-managed contexts, repeated settlement boundaries, and sequences involving venues such as Cetus, with one example combining Bluefin and Cetus.
The first transaction, 557gpooj, linked 12 calls. Its detail describes two separate router contexts, three exchange-related calls in each, and settlement steps returning USDC and SUI balances. The sender-boundary movement was +0.000630206 SUI, but the transaction narrative explicitly leaves the swap outcome unresolved. Reaching those calls therefore does not establish an exchange.
At the other extreme, F94QcTRW prepared a router context, ran Cetus stages, created a fresh context, and combined Bluefin and Cetus activity before another confirmation boundary. It completed without an execution error, yet its stored explanation still does not establish an exchange.
The remaining 241 transactions show the same broad family of activity without an asserted whole-transaction purpose. Many linked router, pool, and settlement calls through connected handoffs; others reached venue functions whose exact meaning had not been authored. This is a knowledge boundary, not evidence that the transactions contained no route activity.
The failure loop
Thirty-one of the 260 transactions failed. Thirty stopped at the same guard: err_amount_out_slippage_check_failed in revision 0xde5d…e39640. One stopped inside pool::swap_in_pool. The first failed example, F4v2vhYS, reached three exchange-related calls and a settlement call before aborting; six submitted steps did not run. The latest row, DpZprTPP, followed an eight-call route through NAVX and SUI, then aborted at a later settlement boundary with one step remaining.
Sui rolls back application effects when execution aborts. These rows therefore prove attempted route construction and the point of failure, not completed swaps or durable application effects. The repeated slippage guard suggests a persistent route-acceptance problem within this window, but the evidence does not identify its off-chain cause.
What moved
All recorded sender movements were SUI, and the sender paid its own gas in all 260 transactions; none were sponsored.
Across the complete history, sender-boundary movement evidence shows 0.0853202 SUI in and 0.01674836 SUI out, for a net of +0.06857184 SUI. Separately, gas accounting shows 0.143488012 SUI out and 0.002508472 SUI in, for net gas of −0.14097954 SUI. These evidence categories are separate and must not be added together. They also do not establish profit: the route outcomes remain unresolved, and no prices or cross-asset valuation exist.
Movement evidence was present for all 260 transactions, with no omitted movement sources. That makes the SUI boundary totals well covered, while still leaving the economic meaning of the multi-asset route calls unresolved.
The useful exits
557gpoojis the clearest successful route narrative: two router contexts, repeated Cetus stages, and an unresolved exchange outcome.F4v2vhYSshows the recurring slippage failure after route calls and settlement preparation.DpZprTPPshows that the same failure mode was still present in the final transaction of the address’s frozen history.
The address is best understood as a varied route-construction identity with a narrow set of recognized patterns, many unsupported venue combinations, and a recurring slippage rejection—not as a proven trader, operator, or profitable strategy.