For the address-wide frozen-window history, 0x5776046879716d97cec388ad6028f4d36c8b800ff872c1faec0d36d74e527ccc appeared in 996 transactions between 21:30:12 and 23:37:40 UTC on 2026-07-19. Every one succeeded. The repertoire is unusually coherent: 307 transactions added liquidity to liquidity-bin positions, 283 routed value, and exactly 114 each harvested assets, closed liquidity positions, and executed the paired close-position workflow.
That repetition is the character. The address moved at a median gap of 7.588 seconds, with 90% of gaps no longer than 9.606 seconds and a longest idle period of 24.614 seconds. Its busiest minute contained nine transactions. This regularity is consistent with scheduled or automated execution, but the chain evidence establishes neither a bot nor a human operator.
The recurring sequence
These counts use the complete 996-transaction address history. The 307 liquidity-add transactions came from two recognized compositions: 224 used sui/execute-lb-pair-add-liquidity/roster-f0037/v1, while 83 used sui/execute-lb-pair-add-liquidity/roster-f0064/v1. Their authored descriptions connect source funding to an opened position and a liquidity addition, sometimes followed by delivery of the resulting position object.
The 283 routed transactions were mostly sui/execute-swap-route/roster-f0095/v1—254 instances. Another 23 used sui/execute-swap-route/roster-f0040/v1, and six used a packed route composition. The route records show funding splits, venue calls, confirmation, settlement, and transfer. They do not, by themselves, establish an economic exchange.
The three 114-transaction groups form a striking one-for-one exit pattern: asset claims, paired position closes, and the longer close-liquidity-position sequence. That is consistent with repeated position maintenance and removal. It still does not identify the underlying strategy, the market, or whether any position was profitable.
The repertoire stayed stable across the address's active hours. In the 21:00 bucket, 75 of 237 transactions added liquidity and 65 routed value. In the 22:00 bucket, the corresponding counts were 140 of 472 and 138 of 472. In the 23:00 bucket, they were 92 of 287 and 80 of 287. Exit activity appeared throughout the latter two buckets rather than replacing the add-and-route rhythm.
What moved
These figures use the complete 996-transaction history. Gas accounting and asset-holding accounting are separate; they must not be added together because the same SUI charge can appear in both views.
- Gas-side SUI movements show 1.762736756 SUI out and 0.711748480 SUI in, for a net gas movement of −1.050988276 SUI.
- Sender-bound SUI holding movements show 213,402.264934300 SUI in and 213,402.263215878 SUI out, for a net of +0.001718422 SUI across 995 transactions.
- USDSUI holding movements show 254,297.520890 USDSUI in and 252,114.235667 USDSUI out, for a net of +2,183.285223 USDSUI across 312 transactions.
- USDC holding movements show 252,846.768251 USDC in and 250,664.678262 USDC out, for a net of +2,182.089989 USDC across 312 transactions.
- LBTC holding movements were nearly balanced: 0.16799967 LBTC in versus 0.16799968 LBTC out, a net of −0.00000001 LBTC across 342 transactions.
- The
0x549e8b…CERTasset and the0xaafb10…BTCasset were each balanced in the aggregate raw movements recorded for 342 transactions.
These are boundary movements attributed to the sender. They are not prices, cross-asset valuations, or proof of profit.
Three concrete moments
The latest detailed stream contains 500 transactions, capped to activity from 22:33:03 to 23:37:40 UTC. It mirrors the address-wide pattern: 155 liquidity-add transactions, 146 routes, 57 claims, 57 paired closes, and 57 close-liquidity-position transactions. The remaining 28 rows had structural descriptions but no named operation.
At GvCutRvS, the latest transaction in that capped stream, the address claimed USDC and USDSUI, removed liquidity, and then closed the position. The sender-bound result was +2,183.285277 USDSUI, +2,182.089989 USDC, and +0.003102544 SUI. The transaction explains the sequence, but not how much of each returned asset represented fees, principal, or anything else.
At 9jjcZA7Y, a route touched the 0xaafb10…BTC asset and LBTC. The sender-bound movements were −11,566 raw units of the former and +0.00011514 LBTC, alongside +0.000364436 SUI. The route completed its recorded steps, but the transaction's own explanation explicitly withholds the claim that an exchange occurred.
At 26z24hXA, the address opened and funded a liquidity-bin position. The boundary movements were −0.005260704 SUI, −128,956 raw units of 0xaafb10…BTC, and −0.00128391 LBTC. The evidence establishes the deposit workflow and delivery of a position object; it does not establish the later value of that position.
The clearest reading is therefore bounded: this on-chain identity repeatedly opened, routed, maintained, and closed liquidity positions at a highly regular cadence during this frozen window. It paid its own gas, never failed in the 996 observed transactions, and moved substantial priced-by-registry token quantities at the boundary. The evidence does not establish who controlled it, why the cycle ran, or whether it made money.
Useful exits are GvCutRvS, 9jjcZA7Y, and 26z24hXA; the main reusable compositions are sui/execute-lb-pair-add-liquidity/roster-f0037/v1, sui/execute-swap-route/roster-f0095/v1, sui/claim-assets/roster-f0060/v1, sui/close-liquidity-position/roster-f0058/v1, and sui/execute-lb-pair-close-position/roster-f0061/v1.
Scope note: aggregate counts and movements above use all 996 transactions attributed to this address in the frozen atlas window. The concrete examples and latest-stream repertoire use the separate capped stream of 500 most recent transactions.