For just over ten and a half hours on 19 July 2026, this address did one thing: it repeatedly executed a route touching TRUTH and USDC. The complete history contains 1,600 stored transactions, all successful, all paid by the sender, and all carrying the same asserted behavior: execute-swap-route.
The repetition is striking. The median gap was 1.010 seconds, although the mean was 23.799 seconds because of longer pauses. The longest idle period was 758.210 seconds—about 12 minutes 38 seconds—and the busiest minute contained 22 transactions. That cadence and the repeated command structures are consistent with automated execution, but the evidence does not establish who operated the address or why.
One route, three shapes
The whole history used two route variants. The ordinary variant accounted for 1,592 of 1,600 transactions; eight used a second variant. Across those variants, the address used three exact command shapes.
The common shape merged an input coin, created an empty companion coin through the Sui framework, then called gateway::swap_assets in package revision 0xd075338d105482f1527cbfd363d6413558f184dec36d9138a70261e87f486e9c. In the first transaction, GBZgSbDz, the recorded boundary movements were −4,000 TRUTH and +49.123631 USDC, alongside a net gas figure of −9,219,240 MIST. The transaction detail explicitly says the route reached its gateway emission point but cannot distinguish an exchange from a return without exchange.
The late-history example 5YmvV9Uv used the shorter two-step shape: it created the empty coin and then called the gateway. Its boundary movements were −4,000 TRUTH and +51.731105 USDC, with net gas of −41,368 MIST.
The rare deviation is visible in 7xLwUTVM, one of the eight transactions using coverage93-r054-whole/v1. It added a coin split before creating the companion coin, preparing three supporting values instead of two. Its boundary movements went the other direction: +4,000 TRUTH and −51.741452 USDC. That is a meaningful structural exception, but it still does not prove that an exchange occurred.
The address's latest-500 transaction stream covers 18:44:21–23:36:06 UTC. Within that capped stream, 495 rows used the common route variant and five used the split-coin variant. The stream's largest absolute gas figure was −13,822,928 MIST in 8qheeaMx.
What moved
These figures use the complete 1,600-transaction history. Every transaction had recorded sender movements, with no omitted movement sources.
- TRUTH: 3,180,000 entered and 3,220,000 left through the sender's holding evidence, for a net of −40,000 TRUTH.
- USDC: 41,491.198602 entered and 40,939.942172 left, for a net of +551.25643 USDC.
- SUI gas: 1.861199184 SUI went out against 1.530505480 SUI in, for a net gas outflow of 0.330693704 SUI.
The same SUI boundary change also appears in holding evidence, so those two SUI figures must not be added together. More importantly, the TRUTH and USDC totals are boundary movements, not a profit statement. The stored meaning does not establish an exchange outcome, and there are no prices with which to compare the assets.
The bounded conclusion
This on-chain identity looks like a tightly repeated route executor: one sender, one gas owner, one behavior, two nearby route variants, and a roughly one-second median cadence. It repeatedly prepared values for a gateway call involving TRUTH and USDC, sometimes receiving one asset at the transaction boundary and sometimes the other. The evidence supports route execution and those bounded movements. It does not establish a completed exchange, profitability, beneficial ownership, or an operator.
Useful exits are GBZgSbDz for the first recorded route, 7xLwUTVM for the rare split-coin shape, 5YmvV9Uv for the final route, and the gateway revision 0xd075338d105482f1527cbfd363d6413558f184dec36d9138a70261e87f486e9c.