For roughly ten and a half hours on 2026-07-19, this address sent 606 transactions at an almost metronomic pace: the median gap was 59,992 milliseconds, the 90th-percentile gap was 119,464.4 milliseconds, and the longest recorded pause was 239,949 milliseconds. Every transaction succeeded at execution, and the longest uninterrupted run of successes was all 606 transactions.
This is an on-chain address, not a proven person, company, operator, or bot. Every transaction was sponsored by the same separate gas owner, 0x39b9e5942df9a4686ebe727534077281d6adcee15a9bb74d3e052e56d78b2744. Across the complete history, the recorded net gas total was 2,776,905,360 MIST; because the gas owner was separate, that figure does not establish that this sender paid it.
The routine
The clearest activity was ADRENALINE issuance. Across the complete 606-transaction history:
- 317 transactions invoked the single-call
execute-adrenaline-mintbehavior. - 98 transactions grouped three ADRENALINE mint calls into one batch.
- The remaining 191 transactions reached creation calls whose complete purpose was not established.
The two mint behaviors account for 415 of 606 transactions, or 68.5% of the whole history. The system’s contract analysis describes the ADRENALINE package as a centrally controlled token whose treasury capability governs issuance. That supports describing these rows as successful issuance requests, not as proof of who ultimately received the tokens or what they were worth.
The latest-500 transaction stream covers 2026-07-19 14:44:11.350–23:37:11.955 UTC. It shows the same character: 277 single-call mint transactions, 79 three-call batches, and 144 creation calls without a complete purpose. All 500 were sponsored and none failed.
What the examples actually prove
The final transaction, 9oC1Mwrw, reached the ADRENALINE mint path at 23:37:11.955 UTC. Its detail records one submitted amount of 500, but explicitly says that this is not proof that the amount was spent or that output was produced. The evidence establishes issuance at the mint operation while leaving ultimate token custody unresolved.
Three minutes earlier, 4jzxgvqc ran three mint calls in sequence. The recorded submitted amounts were 300, 300, and 3,000. Those are call observations, not a sender value flow, and the transaction does not establish who received the newly issued assets.
The notable exception is 2f7Diwx, a creation call to athlete_sbt::mint_update_cap through a second package revision. Its record identifies the call but does not establish the transaction’s broader purpose. That pattern accounts for the 191 unexplained creation calls in the complete history, rather than being folded into the minting total.
The money boundary
No sender movements were proven for this address in either the complete-history aggregates or the latest-500 stream. That means the evidence does not support reporting an amount of ADRENALINE received, spent, transferred, or retained by the sender. The submitted mint amounts remain call-level observations, not a balance statement, payout, or profit measure.
The address called the analyzed ADRENALINE package revision 0x3ebb28…cfb652 in 550 of 606 transactions. The other 56 called 0x856629…f7f514, the revision associated with the creation-call residue. Activity remained steady across the window: the busiest minute contained only three transactions, and the hourly mix shifted gradually from more unexplained creation calls early on toward a stronger dominance of single-call minting later.
The safest description is therefore narrow but strong: this address repeatedly submitted successful, sponsored calls to an ADRENALINE mint path at roughly one-minute intervals, alongside a substantial set of creation calls whose complete purpose remains unresolved. The record says nothing about the sender’s identity, the recipients’ identities, token market value, or profitability.