For the frozen window on 2026-07-19, this address made 77 transactions between 13:10:05 and 23:35:35 UTC. The activity was sparse and irregular: the median gap was 354.9 seconds, the 90th-percentile gap was 986.3 seconds, and the longest idle period was 38 minutes 39 seconds. It does not read like one repeated transaction. Across those 77 rows, the ledger contains 71 distinct command shapes.
The address’s clearest supported theme is multi-step swap routing around a vault. MotiveLayer asserted execute-swap-route for 18 transactions, spread across 14 patterns. That label describes the attempted composition; it does not prove that an exchange completed. The other 59 transactions received no asserted whole-transaction purpose, although many still expose connected calls and partial value movements.
The address paid its own gas in every transaction. There was no sponsored activity, and the gas owner matched the sender throughout this window.
The repeated break point
Failure dominates the history: 46 of 77 transactions failed. Of those failures, 44 stopped at vault::deposit_with_threshold_and_event; the remaining two had an unrecorded abort location. The longest consecutive failure run was seven transactions, while the longest consecutive success run was five.
That failure location matters. In Sui, an aborted programmable transaction rolls back application effects. Reaching a withdrawal, adapter swap, or deposit call therefore proves an attempt, not a persisted vault round trip.
The first transaction, [9psxiDHB](9psxiDHB), is a useful miniature of the problem. It withdrew a SUI balance, passed value through DEEP, WAL, and USDC-related calls, then reached a vault deposit guarded by a 5 SUI minimum. It aborted at the deposit. The sender-level evidence records only −0.000967792 SUI, and the stored narrative explicitly leaves the swap outcome unresolved.
A contrasting row is [CrHDFw4e](CrHDFw4e). Its approved pattern, sui/execute-swap-route/packed-e118-3e708b9d0fa2-3c4b94921bb8-3c4b94921bb8/v1, describes a vault withdrawal followed by alternating adapter directions and a return to deposit. The transaction was structurally understood, but the recorded narrative still says that execution does not establish an exchange. Its observed sender movement was −0.000528488 SUI, attributable to the transaction boundary rather than to a proven trade result.
The exceptions are more revealing than the average
The largest absolute gas charge was [HQEbnjy9](HQEbnjy9): 51,321,828 MIST. It submitted 85.885714284 SUI and used the same amount as a minimum-output guard, then aborted at the vault deposit. That is a large attempted route, not evidence of an 85.885714284 SUI exchange or loss.
At the other extreme, [8bR9tJfW](8bR9tJfW) contains only a vault withdrawal and an object transfer. Its purpose remains unresolved, but sender-boundary evidence shows 2.994792868 SUI entering holding value while 0.005207132 SUI left in gas. The latest row, [3iJniK6p](3iJniK6p), similarly has no asserted purpose: it records a multi-step path touching NS, DEEP, USDC, and STSUI, with −0.005676124 SUI and +7,259 units of the registry-displayed 0x514549…NS asset.
What actually moved
The whole-history brief reports these movements by evidence category; the categories must not be added together:
- SUI gas: gross out 155,894,530 MIST, gross in 530,536 MIST, net −155,363,994 MIST.
- SUI holding: gross in 2.995323404 SUI, gross out 0.150687403 SUI, net +2.844636001 SUI.
- DEEP holding: +23,636 raw units.
0x514549…NSholding: +34,803 raw units, with no approved display denomination.
These are boundary movements, not prices, profit, or proof that the route exchanged one asset for another. The evidence supports a sparse set of vault-funded, multi-venue attempts with substantial unexplained composition and a recurring failure at the terminal deposit. It does not establish who operated the address, whether the activity was automated, or whether any route was profitable.
The aggregate brief covers the address’s whole stored history. The ledger and detail stream is capped at the latest 500 transactions; this address has only 77 eligible transactions, so all 77 appear in that stream. The corpus is frozen to this window and says nothing about activity before or after it.