THE DOSSIER · one of 50

A 21.8-second oracle metronome

0xb2ef2d4f0ce1193041a89cc40ba75b8cfa24cfa7ce5ce6ff1702409a7fc05fad
1,750 transactions in the window · browse every one →

For 10 hours and 35 minutes, this address did one thing: it sent 1,750 update-price transactions. They arrived at an almost mechanical rhythm, with a median gap of 21,771 milliseconds and a 90th-percentile gap of 22,080 milliseconds. The pattern resembles a dedicated oracle-maintenance sender. It does not establish who operated the address, whether it was automated, or whether the submitted prices were economically correct.

The rhythm never changes

These whole-history figures cover all 1,750 transactions, from 2026-07-19 13:02:08 UTC through 23:37:34 UTC. Every transaction had no execution error, and every one followed the same asserted workflow. The longest idle period was only 22,976 milliseconds; the busiest minute contained three transactions. Hourly counts stayed between 160 and 166 until the final partial hour, with no visible shift in repertoire.

The detailed stream is separately capped at the latest 500 explained transactions, covering 20:36:23 through 23:37:34 UTC. All 500 preserve the same behavior, command shape, package revision, and timing pattern.

One guarded call, repeated

The representative transactions DjAx2BQj, 3kW9VUEJ, and 43wBxdEN each contain one call to 0xeff48c7e821fa7e96b390c6c8c332e6ddd86b970dd94f44c4ef376e23a739fb2::nautilus_oracle::update_prices.

The stored explanation describes this as a guarded data-maintenance path: an enclave-authorized reporter submits a vector of market observations, subject to signature, shape, price, session, and timestamp checks. A passing call may insert or replace oracle records. The transaction detail is explicit about the boundary, however: execution alone does not establish that stored observations changed. So this dossier can say that the address repeatedly ran the oracle-update call; it cannot say that a particular price record was updated, that the values were correct, or that any market trade occurred.

The bounded money story

Across the whole history, recorded sender movements contain SUI outflows of 3,034,186,880 MIST (3.03418688 SUI) in gas accounting and the same amount in holding-balance accounting. Those are overlapping evidence categories, not two costs to add together.

In the latest-500 stream, every row records 1,734,380 MIST of SUI outflow in each category, for 867,190,000 MIST (0.86719 SUI) of gas across that capped slice. No other sender asset movement appears in the available record, and there are no prices with which to estimate dollar value or profit.

The gas owner is the sender itself, and none of the 1,750 transactions is sponsored. That identifies the on-chain payer, not a person, organization, or operator.

Follow the thread

Start with DjAx2BQj at the address's first recorded activity, compare it with 3kW9VUEJ at the beginning of the latest-500 slice, and finish at 43wBxdEN. The reusable explanation is sui/update-price/nautilus-oracle-vector-batch/v1, called through revision 0xeff48c7e821fa7e96b390c6c8c332e6ddd86b970dd94f44c4ef376e23a739fb2.

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