For the entire frozen window, this address did almost nothing except maintain DeepBook activity: 41,000 limit-order placement calls and 33,593 selected-order cancellations. The cadence and repetition are consistent with automated order maintenance, but the evidence does not identify a person, operator, or profitability.
For context, Sui describes DeepBook as an on-chain central limit order book. [Sui documentation](https://docs.sui.io/assets/files/deepbook-3e24e6e1deeb8cd860682c1fb473b597.pdf)
The rhythm
Across all 75,122 stored transactions from 13:01:49 to 23:37:42 UTC, the median timestamp gap was 0 milliseconds because many transactions share timestamps; the mean was 508 milliseconds and the 90th-percentile gap was 1.085 seconds. The longest idle period was only 92.2 seconds. The busiest minute was 18:08 UTC, with 760 transactions, and the longest uninterrupted run of successful executions was 26,889 transactions.
The hourly mix barely changed. Placement calls remained near 54–55% and cancellations near 44–45% in every hourly bucket. This is repetition as a finding: the address maintained the same two-part routine throughout the window.
Two acts, not five
Using 74,725 rows eligible for semantic behavior counts, placement calls accounted for 41,000 rows, or 54.9%, while selected-order cancellations accounted for 33,593, or 45.0%. Another 128 rows had no behavior claim, so they should not be turned into an invented “other” category.
The only additional asserted behaviors were two owner-authorized placement attempts, one native-coin consolidation, and one asset-transfer operation. The two placement attempts—EY7npjQa... and BZ7aNgzV...—failed at order_info::assert_execution and rolled back. BUcuhKa... merged native coin objects. 5ExdLLmb... performed an asset-transfer flow after a native split; that record does not establish an economic outcome or recipient benefit.
The main DeepBook revision, 0xf48222c4…96f621e, was called in 74,993 of the 75,122 transactions. A second revision appeared 127 times. The address paid its own gas in every stored transaction; none were sponsored.
The exceptions and what they prove
4AgKkfwh... is a representative placement call in the latest stream. It submitted 64,529 USDC per WBTC and a 0.00554 WBTC size. The transaction narrative treats that figure as a resting price, not an execution price, and explicitly says the call does not prove that the order entered or remained on the book.
8jtmyizC... is a selected-order cancellation in the SUI/suiUSDe book. It demonstrates authorized selection processing, but not that every requested identifier matched a live order.
The failure 63rEZyDT... shows the other side of the record. Execution was cancelled because a required shared object was congested, so no application behavior was asserted. Across the entire history there were 36 failed transactions: 34 carried no recorded abort site, while two stopped at 0xf48222c4…96f621e::order_info::assert_execution. Failure is separate from how completely a transaction can be explained.
The money story
The complete history records sender-bound SUI movement for all 75,122 transactions, with no omitted movement sources.
- Gas accounting: 4.222380788 SUI in, 84.622104278 SUI out, net −80.39972349 SUI.
- Holding accounting: 23,270.37121842 SUI in, 23,350.77094191 SUI out, net −80.39972349 SUI.
Those two totals must not be added: the gas charge also appears in the holding accounting. No prices are present, so these figures cannot establish profit, loss, or an exchange outcome.
The capped latest-500 stream covers 23:35:18.714–23:37:42.097 UTC. All 500 transactions completed successfully and had purpose descriptions: 271 placement calls and 229 cancellations. Their gas outflow was 0.534022426 SUI. The same amount appears in the holding accounting as well, so it is still one charge viewed two ways.
Bottom line
This on-chain identity resembles a continuously running DeepBook quoting or order-maintenance process: extremely fast repetition, a stable placement-to-cancellation ratio, and almost no deviation. That interpretation does not establish who controlled it, whether the orders filled, or whether the activity was profitable.
Useful exits are 4AgKkfwh... for a placement example, 8jtmyizC... for selected cancellation, 63rEZyDT... for congestion failure, and the reusable keys sui/place-limit-orders/deepbook-owner-proof/v1 and sui/cancel-selected-orders/roster-f0002/v1.