For 10 hours and 34 minutes on 2026-07-19, this address repeatedly assembled flash-credit and multi-venue swap routes. Of its 2,548 eligible transactions, 2,255 failed. Only 122 received the system’s named execute-swap-route interpretation. The pattern is consistent with highly automated execution, but the evidence does not establish who operated the address or whether any strategy was profitable.
The complete-history brief covers transactions from 13:02:05 to 23:36:34 UTC. Its rhythm is bursty: the median gap is 0 ms because many transactions arrived together, the mean gap is about 14.95 seconds, and the 90th-percentile gap is 29.52 seconds. The longest quiet period lasted about 13 minutes 23 seconds. The busiest minute, 21:40 UTC, contained 55 transactions. The longest consecutive failure run was 51.
Most routes never received a name
The named route group is small: 122 of 2,548 eligible transactions. The remaining activity was described as connected call compositions without a whole-transaction purpose being asserted. The authored explanations for the named variants repeatedly describe a flash-loan opening, swaps through venues such as Cetus, Bluefin, and a router, followed by a flash close and repayment. That establishes the route structure, not an economic gain.
Even the named group is not synonymous with success. Two of the 122 named routes carried a failure flag despite receiving a complete route interpretation. A route can therefore be structurally understood while still aborting.
The capped transaction stream contains the latest 500 explainable rows, covering 21:42:48–23:36:34 UTC. In that recent slice, 453 failed and 47 did not. Seventeen received the named route interpretation; the other 483 were explained only through their individual steps. This recent slice is not the address’s complete history.
A representative successful route is D2Hmn4iT, at 23:26:34 UTC. It connected eight calls: a flash-credit opening, a Cetus leg, a router return leg, a Bluefin leg, a direct swap, then flash closure and repayment. The detail says the lifecycle closed successfully, but explicitly does not establish an exchange result. The submitted amount was 2.951193078 SUI, while the sender’s boundary movement was −0.002041912 SUI.
The dominant failure mode is much plainer. 37pFkJHa, the first row in the recent stream, opened flash credit and threaded SUI through NAVX, USDC, and SCA calls before stopping because the source coin balance was too small. Application effects were rolled back; the sender’s recorded boundary movement was −0.000486672 SUI. The 2.588909211 SUI submitted amount is not evidence that that value was spent or that output was produced.
A rarer recent shape, CNcFv4SU, reached jk::soa in package 0xd003569a6b95f0c5ccebc1a5f790e49a009c5bf986e30cabe1116bba7e3a3e54, whose role remains unexplained in the stored knowledge. It then stopped at the same insufficient-balance condition. That transaction submitted 1.335735293 SUI and recorded −0.000904744 SUI at the boundary.
The money story is almost entirely gas
Across the complete history, the sender’s proven SUI movement is 1.79747571 SUI out in the gas evidence view. The same amount also appears in a separate holding-evidence view. Those are overlapping observations, not two amounts to add together. No priced value, cross-asset total, or profit calculation is available.
The address itself paid gas on all 2,548 transactions; none were sponsored by another gas owner. That identifies the payer, not the person or organization behind the address. The evidence supports a persistent, bursty route-execution process that repeatedly ran into balance or downstream-call problems. It does not establish identity, intent, or profitability.
For a closer look, start with D2Hmn4iT for a named route that reached its flash lifecycle, 37pFkJHa for the dominant insufficient-balance failure, and CNcFv4SU for the unexplained jk::soa deviation. The reusable route cohort is sui/execute-swap-route/packed-e118-9df2d78eb84a-8d9484dd3ff7/v1.