For roughly ten and a half hours, this on-chain identity explored complicated vault-backed value routes, but the dominant story was uncertainty at the transaction boundary. Of 78 transactions in the complete history—and therefore all 78 rows in the latest-500 dossier stream—47 failed at the same vault deposit function. The activity is consistent with repeated route attempts, but it does not establish who operated the address or whether any exchange or profit occurred.
A sparse, shape-shifting repertoire
The first transaction arrived at 13:03:11 UTC and the last at 23:33:04 UTC. The median gap was 394.463 seconds, the 90th-percentile gap was 1,029.719 seconds, and the longest idle period was 1,676.001 seconds. The busiest minute contained only two transactions. The longest consecutive failure run was seven; the longest success run was three.
The address used 72 exact command-and-call shapes and 20 route variants. Twenty-four transactions received an asserted execute-swap-route meaning. The other 54 had only part of their composition or individual calls explained, so the explorer withheld a transaction-level behavior claim for them. This is a diverse and intermittent repertoire, not one repeated shape at a fixed cadence.
The route meaning is nevertheless recognizable. A typical explained route withdraws value from a vault, passes it through adapter and pool-related calls, then presents the resulting balance to a thresholded vault deposit. The stored explanation describes routing mechanics and custody boundaries; it does not prove that an exchange completed.
The repeated failure point
All 47 failures stopped at vault::deposit_with_threshold_and_event in package 0xf0b2cc…c9d5c6. The address therefore repeatedly reached a terminal vault handoff that did not commit. Because Sui rolls back application effects after an abort, the preceding withdrawals and route calls prove attempted execution, not durable application movement.
The last transaction, CXJ9qguo, is a clean example: it passed through six connected calls, submitted 1.64285714 SUI, and used the same amount as a minimum-output guard before aborting at the vault deposit. Its recorded sender movement was only the 0.00041198 SUI gas charge.
The contrasting successful example, 4YabngTq, withdrew vault-held value, invoked a pool-buy path and opposing adapter directions, and reached the deposit step. It submitted 18.05 SUI and guarded on 18.05 SUI, but the transaction detail explicitly leaves the exchange outcome unresolved. A committed route is not evidence of a completed exchange.
One notable exception, 8ftQsbMN, reached jk::flowxswapv3_0 in package 0xaf7cd4…1884a0, a revision without an authored transaction-level explanation in this view. It continued through additional calls and reached a deposit, but the available evidence does not establish the complete purpose.
What the boundary movements show
Across the complete 78-transaction history, sender-boundary records show:
- Gas category: net outflow of 87,196,102 MIST, or 0.087196102 SUI.
- Holding category: net outflow of 82,851,505 MIST, or 0.082851505 SUI.
- DEEP holding category: 6,532 raw units received in one transaction, displayed as 0.006532 DEEP.
The gas and holding figures must remain separate: the same gas charge can appear in both records, so adding them would double-count. Movement evidence was present for all 78 transactions, with no omitted sources. These figures establish bounded sender movements, not a cross-asset return, exchange result, or profit.
The gas owner was the sender in all 78 transactions, so none of this activity was sponsored. That identifies the payer relationship on-chain; it does not identify a person, company, operator, or bot.
Exits
Start with the first observed shape, GzQ7jg81, or the latest failed route, CXJ9qguo. For the explained successful route, inspect 4YabngTq; for the unexplained package call, inspect 8ftQsbMN. The most representative reusable route variants are sui/execute-swap-route/strict-remap-next-40dfd02a3497/v1 and sui/execute-swap-route/packed-e118-e9cf7ae9ef02-3c4b94921bb8/v1.