For ten hours on 19 July, this address repeatedly attempted flash-funded swap routes, and most of those attempts reached the same repayment wall. Across its complete history in the frozen window, it sent 1,602 transactions: 1,477 failed, or 92.2%. Of those failures, 1,394 stopped at flash_loan::return_flashloan_quote. The pattern resembles repeated route attempts with a repayment bottleneck; it does not establish who controlled the address or whether any strategy was profitable.
A steady rhythm, with one stubborn outcome
The complete-history cadence was irregular but often rapid: the median gap was 1.403 seconds, while the 90th-percentile gap was 65.012 seconds. The longest idle period was 9 minutes 45 seconds. Activity peaked at 62 transactions during 18:08 UTC. The longest consecutive failure run was 58 transactions; the longest success run was only 3.
The repertoire barely changed across the window. execute-swap-route was the only asserted behavior, appearing on 1,374 of the 1,565 transactions that received semantic labeling. The address used its own gas owner on all 1,602 transactions; none were sponsored. That identifies the payer relationship, not the person or system behind the address.
The detailed stream is a separate, capped view of the latest 500 transactions, from 20:50:15 to 23:37:39 UTC. In that stream, 459 failed. The system described the complete route in 441 transactions, while 59 received only a partial or component-level description. Among the failures, 425 reached the same flash-loan repayment call. The latest activity therefore looks like continuation of the same loop, not a change in direction.
What the routes actually attempted
The authored route meanings describe quote-side flash liquidity being passed through combinations of DeepBook, Bluefin, Cetus, and other adapters before returning the borrowed asset and receipt. The route composition proves that those calls were connected; it does not prove the exchange quantities or an economic result.
At 20:50 UTC, transaction Ufqaepvp ran a five-step path: opened flash credit, created a zero-valued support coin, called DeepBook, called Bluefin, and reached repayment. It submitted 5.003787 USDC. The sender boundary showed −0.005970856 SUI and +0.005952 USDC, but the transaction detail explicitly leaves the exchange unresolved.
Near the end of the window, us9mmHTz submitted 142 USDC through a DeepBook–Cetus route and aborted at the same repayment call. Only −0.00038668 SUI is recorded for the sender. The route was reached, but the application effects were rolled back; Sui’s documented all-or-nothing transaction model likewise treats an abort as carrying gas costs without persisting earlier application effects ([Sui protocol paper](https://docs.sui.io/paper/sui.pdf)).
There was a meaningful exception. Hy8m8BUU committed a route involving an exact pool swap, a DEEP support coin, and DeepBook. Its sender movements included +0.007955876 SUI and +85,936 raw NS units. Even here, the stored explanation says execution does not establish an exchange. A committed route is evidence of execution, not proof of a completed trade or gain.
The bounded money story
For the complete history, reported sender movements were:
- Gas lane: −1.728349322 SUI across all 1,602 transactions.
- Holding lane: +0.579669807 SUI in and −1.613042547 SUI out.
- Holding lane: +1.182252 USDC across 89 transactions.
- Holding lane: +0.671512165 WAL across 15 transactions.
- Smaller raw-unit inflows included 175 XBTC, 94,877 NS, 4 WBTC, 0.058972 USDSUI, 1,750,951 XAGM, and 0.01533 DEEP.
The gas and holding SUI figures are separate evidence lanes and must not be added together. No prices are available, and the movements do not establish profit, loss, or a cross-asset exchange outcome. In the latest 500-transaction detail stream alone, the reported gas total was 0.681127573 SUI.
The most revealing fact is not the variety of venues. It is the repetition: 1,394 failures at one repayment boundary across the complete history, with only brief successful runs and no clear repertoire change. The evidence supports a persistent route-attempt pattern at this address. It does not establish an operator, identity, intent, or economic success.
Useful exits are Ufqaepvp for a committed DeepBook–Bluefin route, us9mmHTz for the latest repayment abort, Hy8m8BUU for the unusual NS movement, and the route patterns coverage93-r004, strict-remap-4262650e2e45, and strict-remap-d077d3e29c4d.