THE DOSSIER · one of 50

The four-hour payment-stream metronome

0x165c60b41663e1b45c67422056eeafd14b69208f3f664987bb71e754a1cc9b8b
435 transactions in the window · browse every one →

From 19:37:27 to 23:36:43 UTC on 19 July 2026, this sender produced 435 transactions. Every one was sponsored by the separate gas owner 0x39b9e5…8b2744. The rhythm was steady but not frantic: the median gap was 22.6 seconds, the 90th-percentile gap was 76.5 seconds, and the longest idle period was 80.3 seconds. The busiest minute contained three transactions.

The whole-history record divides neatly. In 182 of 435 transactions, the stored meaning was withdraw-assets: redeem accumulated funds and route the resulting coin into creation of a shared, time-locked payment stream. The other 253 transactions received no whole-transaction purpose. In the latest-500 ledger, which contains all 435 transactions for this address because its history is below the cap, those 253 rows repeat two shapes: 127 two-call sequences that redeemed funds and invoked entry_create_and_share, and 126 one-call entry_revoke transactions described only as authority-revocation calls.

The pattern stayed remarkably stable across the address’s active hours. The sender made 18 meaningful withdrawals among 41 transactions in the 19:00 hour, then 45 of 109 in both the 20:00 and 21:00 hours, 46 of 108 in the 22:00 hour, and 28 of 68 in the final partial hour. This looks like a recurring operational routine, possibly automated, but the evidence does not establish who controlled the address or why the unexplained calls accompanied the withdrawals.

One early withdrawal, EMQ4juek, shows what the system can establish. Its two calls were coin::redeem_funds followed by streaming_payment::create_stream. The transaction detail says the sender-scoped balance was routed into time-based custody rather than sent immediately to the recipient; it also records 60000 as an input to the creation call, not as a proven resulting state change. The recipient’s later receipt is outside this transaction.

The contrast is visible in the neighboring calls. CR5HXBmz returned an MTPS coin from a withdrawal step and passed it to a creation call, but the accepted evidence withheld a complete purpose. NyxsiSd1 ran an authority-revocation call, yet likewise did not establish the larger transaction’s intent. None of the 435 transactions recorded an execution failure, but a transaction having no failure does not make its complete purpose known.

The money trail is deliberately bounded. Across the whole history, the system recorded no sender-bound value movements, so there is no supported asset amount to report and no basis for a profit or payout claim. It did record 1,073,197,248 raw MIST in gas, paid by the separate gas owner on all 435 transactions. Gas and application-value evidence should not be treated as the same thing.

The address is therefore best read as a sponsored, repetitive payment-stream routine with a persistent unresolved companion action. The meaningful withdrawals have a clear asserted purpose; the 253 authority/creation-shaped transactions do not. Nothing in this frozen window identifies the operator, proves a recipient’s later receipt, or establishes an economic result.

Further reading: address 0x165c60b41663e1b45c67422056eeafd14b69208f3f664987bb71e754a1cc9b8b; representative transactions EMQ4juek, CR5HXBmz, and NyxsiSd1; pattern sui/withdraw-assets/roster-f0073/v1.

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