For the frozen window from 13:02:01 to 23:37:39 UTC, this address submitted 1,996 transactions. Its defining activity was repeated flash-loan route execution: 1,607 transactions carried that named route purpose, while 1,815 transactions failed. The failure was remarkably specific: 1,723 failures—94.9% of all failures—stopped at flash_loan::return_flashloan_quote.
That repetition is the character of the address. The median gap across its complete history was 888 milliseconds, with a 90th-percentile gap of 55.9 seconds. Its busiest minute was 17:02 UTC, with 91 transactions, and its longest consecutive failure run was 60 transactions. The repertoire was not literally identical: the stored record contains 291 distinct ordered command sequences, including routes through Cetus, Momentum, Bluefin and DeepBook. But they repeatedly shared the same flash-loan opening, multi-venue route, and repayment boundary.
The latest-500 transaction stream tells the same story. Of those 500 most recent classifiable transactions, 459 failed. The dominant repayment abort appeared in 423 of those failures. In 412 rows MotiveLayer could attach the execute-swap-route purpose; the remaining 88 had lower-level composition descriptions without that broader purpose claim. This latest stream begins at HwDuRFQL and ends at 2JwkTt9Z.
HwDuRFQL is a representative failed attempt. It opened quote-backed flash liquidity, sent SUI through a Cetus conversion and then a Momentum conversion, and presented the resulting SUI with the flash obligation. The repayment call was reached but aborted, so the route’s application effects rolled back. The sender’s recorded boundary movement was only −0.000366084 SUI in gas-related accounting; it does not establish an exchange.
There was a committed exception. In 61kyNbS1, the route opened a flash obligation, passed value through Bluefin and Cetus, and completed the repayment call. The sender-boundary movements were −0.001778772 SUI and +0.0076 USDC. The transaction detail says the exchange quantities were not exposed, so this is evidence of a completed route composition and those boundary movements—not proof of a particular trade, rate, or profit.
Across the complete history, recorded sender movements show −1.794106904 SUI in holding movements and +0.639241806 SUI in the same category, for a holding net of −1.154865098 SUI. Other recorded holding inflows were +0.642621 USDC, +0.24107361 WAL, +0.386374 DEEP and +24 units of an unregistered XBTC asset. Separately, total gas was 1.93832885 SUI, of which failed transactions accounted for 1.292807842 SUI. Gas and holding figures are reported separately because the same gas charge can also appear in holding evidence; they must not be added.
No transaction was sponsored: the sender paid its own gas in all 1,996 eligible transactions. That establishes an on-chain funding arrangement, not the identity of the person, company, operator or software behind the address. Within this frozen window, the evidence is consistent with repeated automated-looking route attempts constrained by a flash-loan repayment condition, but it does not establish who operated the address or whether the successful routes were economically beneficial.
Useful exits are HwDuRFQL for a failed Cetus–Momentum route, 61kyNbS1 for the committed Bluefin–Cetus example, and 2JwkTt9Z for a later DeepBook–Bluefin route that again stopped at repayment.