The minute of 2026-07-19 19:21 UTC was dominated by one on-chain address, but its most instructive failures came from somewhere else. Of 1,250 transactions, 0xcde6dbe0…6c0e04 issued 523—41.84% of the minute—while the frozen corpus baseline for that address is 19.64%. The record names the same address as gas payer throughout those 523 transactions.
Its activity was unusually focused: 287 cancellation attempts and 236 limit-order placement attempts. Across the minute, those behaviors accounted for 630 of the 1,242 transactions carrying a behavior label. Adding 207 price-update transactions and 150 campaign-activity records brings the four leading behaviors to 987 of 1,242 labeled rows.
The order activity was not a simple success story. Transaction 5UJFYVKn submitted 1,044.6 NS at a resting price of 0.01541 SUI per NS after generating an owner proof. That proves an order-placement attempt and its inputs; the detailed evidence does not independently establish that the order remained open or filled. Later, 2zkyqB28 attempted to cancel an identified order, but aborted in big_vector::leaf_remove. Its application changes rolled back, leaving only the gas charge. The minute contains three such DeepBook cancellation failures.
The sharper break involved a different sender, 0x5b7122…d94208. Eighteen of the minute’s 28 failed transactions came from that address. Fourteen stopped at para::repay_loan_base and four at para::repay_loan_quote; fifteen of the 18 carried an execute-swap-route label, while three were not assigned a behavior label. The failures recur across several route compositions rather than appearing as one isolated malformed call.
7aM4N7VK shows the sequence clearly. It opened a short-lived SUI flash credit, converted balances into coins, passed through SUI/CETUS swap calls, converted the result back, and reached the flash-credit repayment step. It then stopped with a Move abort at para::repay_loan_base. The transaction detail explicitly says that application changes were rolled back and that the route does not establish an exchange or economic result. Gas charged for this attempt was 0.002210936 SUI. This is consistent with Sui’s documented all-or-nothing behavior for aborted Move transactions, where application effects do not persist but gas is still charged ([Sui protocol paper](https://docs.sui.io/paper/sui.pdf)).
The money moving through the minute adds a second layer of surprise. Sender-boundary records show 655,789.453455035 SUI moving out and 8.942536327 SUI moving in across 417 SUI holding movements. USDC shows 544,279.63825 out and 0.000802 in across 12 holding movements. These are per-asset boundary movements, not a trade result or profit calculation. The largest individual example, H1tX43kp, is an attempted liquidity-position opening whose boundary record shows -399,988.801672699 SUI and -330,325.02262 USDC. The transaction ran position opening, coin preparation, liquidity addition, and an asset-transfer step, but the retained evidence does not attribute those entire balances to one specific call.
So the minute has two concurrent stories: a highly concentrated stream of DeepBook order-management attempts, and a smaller but persistent set of flash-loan routes failing at repayment. The evidence supports repeated automated-looking execution patterns and repeated retry behavior; it does not establish who controls the addresses, whether any order filled, or whether any swap produced an economic gain.
For a closer look, start with 5UJFYVKn for the dominant order-placement shape, 7aM4N7VK for the repayment failure, and H1tX43kp for the largest recorded SUI boundary movement.