For 10 hours and 32 minutes, this address submitted 432 transactions, all sponsored by the same separate gas owner: 0x4dde35528bf7103801dfd8d5e12a76ae95aafdc1e3a606e0184ab2a3eabd90bf. The repeated activity resembles an automated liquidity or routing workflow, but the evidence does not establish who operated the address, what its overall purpose was, or whether any exchange or withdrawal completed.
The complete frozen-window history contains four recurring kinds of sequences:
- 43 authority-revocation calls.
- 147 verification-then-withdrawal sequences.
- 136 transactions that prepared two supporting values and then ran a deposit step.
- 106 longer liquidity-pool fulfilment paths containing at least one unresolved call.
No transaction received a named whole-transaction activity label. Instead, the system could describe connected call steps: 326 of 432 transactions were limited to that step-level explanation, while 106 contained longer chains with an unresolved call. This is a limitation on the available explanation, not proof that the transactions had no purpose.
The rhythm
The address was active in 251 minutes of the window. Its median gap was 32.0 seconds, the mean was 88.0 seconds, and the 90th-percentile gap was 242.2 seconds. The longest idle period was 14 minutes 2 seconds. Activity peaked at six transactions in the minute beginning 21:18 UTC.
There were 86 distinct command shapes. The most common linked verification-and-withdrawal shape appeared 122 times; another shape prepared supporting values and deposited them 115 times. The repertoire remained broadly stable across the window rather than changing into a new identifiable operation.
What the calls show
The first transaction, 84AyHisD, ran a one-call liquidity_pool::disclaim entrypoint, described as authority revocation. A late example, 8urXEXZ, verified a message and passed it to a withdrawal step. Neither record proves that an authority was actually revoked or that assets were withdrawn.
Near the end, Fn3eDRnU prepared two supporting values, then called token_meta_from_currency and sweep in package 0xccbe154d67f9a4815c8c40790b8feab00283fe7df3413c4016027c4e7195f45d. The stored explanation calls this a deposit step, but it does not establish the complete purpose.
The clearest complex example is 5BMqtGNJ. Its 13-step transaction verified a request, reached liquidity_pool::init_fulfill_swap_request, performed message and price-related preparation, called haedal_hmm_v2::swap, and reached a settlement step returning a SUI coin. It also submitted 18446744073709551615 as an amount. That sentinel-like input is not proof that the value was spent, that an exchange occurred, or that the returned coin was a payout. The transaction later reached liquidity_pool::complete_fulfill_swap_request, but the complete route purpose remained unresolved.
The two most frequently called package revisions were 0xccbe154d67f9a4815c8c40790b8feab00283fe7df3413c4016027c4e7195f45d in 321 of 432 transactions and 0x2c658b2b69e2d4d73bf115cbcefd42449301503047cc91c07ec7f0f35c3697a7 in 111 of 432. These counts overlap with other calls in the same transactions.
The money boundary
The complete address history records 1,135,037,844 MIST in aggregate net gas charges. All 432 transactions were sponsored, so that gas was charged to the separate gas owner rather than the sender address itself.
MotiveLayer recorded no sender movement allocations and no movement-bearing transactions in this scope. That means the stored evidence does not support an amount received, deposited, withdrawn, exchanged, or earned; it should not be read as proof that no asset movement occurred.
The detailed ledger and prose cover all 432 transactions because the address has fewer than the 500-row stream limit. Everything above is therefore bounded to this sender's activity in the frozen 2026-07-19 corpus window, not to a broader identity or history.