THE DOSSIER · one of 50

A late burst of perpetual-market batches

0x2a2195b4e7433cc8c7462b864972f349f7d57b3b0c515ddd86e30a3b3e66d5dd
1,162 transactions in the window · browse every one →

For 10 hours and 28 minutes, 0x2a2195b4e7433cc8c7462b864972f349f7d57b3b0c515ddd86e30a3b3e66d5dd sent 1,162 transactions through one perpetual-exchange package. Most were repeated signed batch submissions; another 80 changed funding and oracle inputs for perpetual markets. The closing burst is consistent with automated strategy execution, but the address does not establish who operated it.

The rhythm changed dramatically

Across the complete history, the median gap was 1.509 seconds, the 90th-percentile gap was 100.981 seconds, and the longest pause was 831.701 seconds. The busiest minute was 2026-07-19 23:25 UTC, with 45 transactions.

The final hour contained 653 transactions. In the detailed stream’s capped latest 500 transactions—from 23:12:17 to 23:36:30 UTC—the median gap was 1.325 seconds. That late concentration is the clearest sign of a tightly scheduled execution phase; it does not prove a human or a bot behind the address.

Four recurring kinds of work

Across the complete history, 302 transactions submitted two-to-four perpetual-market operations, 172 submitted four-operation batches, and 90 submitted paired batches. Together these accounted for 564 of 1,162 transactions.

Another 80 transactions updated a perpetual market’s funding regime. The remaining 518 transactions did not receive a named behavior: 515 were described only as connected contract calls, while three were not recognized beyond that level.

The latest-500 stream is narrower than the complete history. It contains 224 two-to-four-operation batches, 132 four-operation batches, and 62 paired batches. The other 82 transactions had no named behavior. The funding-regime updates belong to the earlier history and do not appear in this late sample.

What the calls establish—and what they do not

Transaction CBFNsRSZ, at 23:36:28 UTC, ran two calls to the exchange’s batch-trade entrypoint. Its explanation says the submissions were signed perpetual-exchange operations, but explicitly does not establish that any particular order filled.

9UuFrZiJ, seven seconds earlier, ran four calls through the same entrypoint. The repeated structure distinguishes it from a single strategy call, but execution alone still does not show that an order filled.

The different side of the address appears in Huq9t65U, at 23:00:22 UTC. It called set_funding_rate through the exchange’s operator-authorized path. That changes market funding and oracle configuration; it does not, by itself, show a payment, receipt, or account settlement.

The late stream also contains less-complete explanations. 47Nu5nG4 ran one strategy-execution call, but the connected steps did not establish the transaction’s complete purpose. This is a limitation of what was explained, not evidence that the call failed: all 1,162 transactions in the complete history have no recorded execution failure.

The money is gas, not a profit statement

For the complete history, the stored sender-movement evidence records only SUI gas: 11.732613088 SUI out, 0.00221964 SUI in, for a net outflow of 11.730393448 SUI. Every transaction had recorded gas movement, and no movement sources were omitted.

Those figures describe gas charged to the sender. They do not establish the value of any perpetual-market operation, whether an order matched, or whether the address made or lost money. No prices or cross-asset valuation are present.

The bounded character

This address looks less like a wallet performing occasional trades than a transaction endpoint for a scheduled perpetual-market workflow: long quiet gaps in the broader window, followed by a dense final run of two-, three-, and four-call submissions. It also carried out a separate series of funding-regime changes. The evidence supports that operational resemblance, while leaving the controller, economic beneficiary, and outcome of individual orders unresolved.

The useful exits are CBFNsRSZ for a paired batch, 9UuFrZiJ for a four-call batch, Huq9t65U for a funding-regime update, and package revision 0x11d01c93c0461f8f505c993e48734b364a95fa7b32c7956e3bd58d93d27d0892 for the shared exchange mechanics.

Dossiers are AI-authored readings of one address's stored window. They describe observed behavior — never operators, identity, or profit the evidence doesn't establish.

everything this address did → all dossiers the shelf