At 19:19 UTC, one on-chain address accounted for 543 of 1,255 eligible transactions—43.3% of the minute. Across the frozen million-transaction corpus, that same address accounts for 196,441 transactions, or 19.6%, making this minute unusually concentrated. The address is an on-chain identity; the evidence does not establish who controls it.
The activity was tightly repetitive. Among the 1,170 transactions with enough evidence for a semantic label, cancellations led with 270, followed by limit-order placements with 262 and price updates with 211. Together, those three behaviors made up 743 of 1,170 labeled transactions, or 63.5%. Within the dominant address’s 543 transactions, 247 were cancellations and 215 were placements. Its timing—median gap 0 ms, mean gap 47.6 ms, and longest idle only 444 ms—resembles batched or automated execution, but does not prove that the address is a bot or identify an operator.
The minute’s largest concrete movement came from FwPRnycB. At 19:19:53.838 UTC, the transaction ran a reward-claim call followed by a liquidity-position closure. The sender-boundary movements were +254,586.427390024 SUI and +210,246.337053 USDC, alongside 0.001524084 SUI of gas. Across all senders in the minute, holding movements totaled 519,689.991700896 SUI in and 511,567.941345217 SUI out, for a net +8,122.050355679 SUI; USDC movements totaled 421,107.920189 in and 420,997.034542 out, for a net +110.885647 USDC. These are boundary movements, not prices, profit, or proof that the reward call collected anything.
The dominant order-book rhythm is visible in 4SJC759S. Its two-step shape generated an owner proof and passed it to an order-cancellation call for an NS/SUI order. The record binds a resting price of 0.01531 SUI per NS and resting size of 1,051.1 NS. Those values describe the order being targeted; they do not establish that it traded.
Failure was present, but mostly before a named behavior could be assigned: 121 of 1,255 eligible transactions failed, a 9.6% rate, compared with 8.36% across the corpus. Eighty-one of those failures were marked unrecorded, all from the dominant address, and shared the same repeated DeepBook shape as the owner-proof cancellation sequence. The remaining named failures clustered around repayment boundaries: 15 at repay_loan_base, 13 at repay_loan_quote, 10 at return_flashloan_quote, and two at reward distribution.
DptpuYEm shows what that failure looked like. It prepared a flash-loan route through SUI, CETUS, and USDC, submitted 0.75345397 SUI at the repayment step, and stopped at repay_loan_base with Move abort code 401. The record says application effects were rolled back and that the reached calls describe an attempted route rather than a completed exchange.
For a closer look, follow FwPRnycB for the large position-closure movement, 4SJC759S for the repeated DeepBook cancellation workflow, or DptpuYEm for the failed flash-loan route. The reusable patterns are sui/close-liquidity-position/d075-gateway/v1 and sui/cancel-order/deepbook-owner-proof/v1.