Sixty sparse transactions took 58 different paths

For this frozen window, 0x5e9221…df4cea3 looks less like a repeated routine than a sampler of multi-venue routes: 60 transactions, 58 distinct ordered call sequences, and only three transactions with an asserted operation. The activity spans 13:27:42–22:52:28 UTC on 2026-07-19, with a median gap of 213.6 seconds and a longest idle period of about 74 minutes. The evidence does not establish who controlled the address or whether any route was profitable.

A repertoire of one-offs

These figures use the address brief’s complete 60-transaction history; the latest-500 ledger and detail streams also contain all 60 because the address has fewer than 500 transactions.

Forty-one transactions were described only through connected calls, and 16 received an incomplete whole-transaction explanation. Three carried an asserted purpose:

• Two matched transfer-assets through the native-split/v1 pattern. Its authored meaning describes splitting an asset and transferring the resulting objects to a resolved recipient, although the row-level evidence does not establish a change in custody when the recipient is the sender.
• One, KnzoTkEZ, matched execute-swap-route through the approved Cetus–Bluefin–Cetus route pattern. Its detail identifies the shared route context and final confirmation, but still says execution does not establish an exchange.

The remaining 57 transactions do not carry an asserted operation. Many are clearly exchange-related compositions, but that is a description of their calls, not proof of an exchange. Fifteen rows also contain unresolved exact functions, including repeated fullsail::swap, kriya_amm::swap, flowx_clmm::swap, and Haedal swap calls.

The first transaction, H1BJSxxK, linked 18 calls and ended with a sender boundary change of +21,135.402034602 NAVX and −157.030245 USDC, alongside −0.00285676 SUI. Its detail explicitly withholds an exchange claim. The last, 4137tG1S, linked 11 calls, reached fullsail::swap without a supported explanation, and recorded −1,044.73 NAVX, +9.856167 USDC, and −0.001075232 SUI. These movements describe what changed at the transaction boundary; they do not identify which call produced the change.

One abort, and a clear stopping point

One of the 60 transactions failed. 46feb4Eb reached a settlement call and then stopped at err_amount_out_slippage_check_failed in the router. The remaining submitted step did not run, and application effects were rolled back. The sender record shows −0.000869988 SUI for that transaction. That SUI amount appears in both the gas and holding evidence, so those records must not be added together.

The failure rate is therefore 1 of 60, or 1.7%. Structural explanation and execution outcome are separate: a transaction can have a detailed call description while still aborting, and a route-like composition can complete without the stored meaning establishing an exchange.

What moved

Across the complete history, the address brief reports these sender boundary movements. Values are grouped by evidence category; categories are not additive.

• SUI used for gas: 0.006368204 in, 0.109430268 out, net −0.103062064 SUI across 60 transactions.
• SUI in holding evidence: 0.006368204 in, 0.109430272 out, net −0.103062068 SUI across 60 transactions.
• NAVX in holding evidence: 189,445.176684529 in, 235,573.023647024 out, net −46,127.846962495 NAVX across 59 transactions.
• USDC in holding evidence: 1,729.614962 in, 1,588.538642 out, net +141.07632 USDC across 57 transactions.
• DEEP in holding evidence: 0.412675 in and no recorded outflow across two transactions.
• An unregistered asset shown as 0x514549…NS: 27,350 in across one transaction.

These are bounded asset movements, not a profit calculation. There are no prices, and opposite-signed movements in NAVX and USDC do not by themselves prove a trade.

The largest native gas charge in the latest-500 stream was 5zZKL5Ag, at 11,818,768 MIST. That row also recorded +7,866.212935901 NAVX and −70.798025 USDC at the sender boundary, while its route explanation remained incomplete.

The character of the address

Within this frozen history, the address is sparse, irregular, and highly path-diverse. It concentrated activity into a handful of busy minutes—the busiest contained only two transactions—then produced long gaps and new call sequences. The strongest supported description is not a stable named strategy but repeated attempts to compose asset routes across different venues, with knowledge gaps preventing a transaction-wide interpretation in most rows.

The useful exits are H1BJSxxK for the first unresolved route, KnzoTkEZ for the one asserted Cetus–Bluefin–Cetus composition, 46feb4Eb for the slippage abort, and 4137tG1S for the latest unresolved fullsail::swap route.