For roughly 38 minutes, this address did one thing repeatedly: submit the same two-call transaction shape, x::g followed by x::Aa_, from revision 0xdfba30638e09733001822640b81772ddc9362c187c1a19f7a9901f385dfdcaf9. The calls have no authored explanation, so the evidence does not establish an action, purpose, operator, or economic result.
The complete frozen history contains 8 eligible transactions. Five failed. Four of those failures stopped at 0x1e4a13a0494d5facdbe8473e74127b838c2d446ecec0ce262e2eddafa77259cb::logic::execute_liquidate; the fifth was canceled before execution because shared objects were congested. The capped latest-500 ledger/detail stream contains 7 rows: four failures followed by three transactions with no recorded execution error, although those three still have no established purpose or outcome.
A burst, then silence, then another burst
The first transaction arrived at 2026-07-19 18:55:53.991 UTC; the last arrived at 19:33:53.563 UTC. Four transactions landed in the busiest minute, and the longest idle period was about 37 minutes 56 seconds. Across the full history, the median gap was 290 milliseconds but the 90th-percentile gap was about 15 minutes 12 seconds. The sequence therefore looks bursty rather than continuously active: four failures in the opening burst, three unexplained non-failing attempts near the end, then one final congestion cancellation.
The first failure, 2djy9hri, reached both calls before a Move abort with code 1606 at execute_liquidate. The application effects were rolled back; reaching the calls proves an attempt, not a completed liquidation. A later transaction, FeCQrBDa, used the identical shape and revision, had no execution error, and still only supports a boundary movement of −0.0415832 SUI. The final transaction, DbqaRiK2, never reached a safely attributable command because required shared objects were congested.
The money is almost entirely execution cost
Across all 8 transactions, the recorded gas flow is −6.737928754 SUI. The separate holding record shows −6.737928759 SUI; these lanes overlap and must not be added together. The flow tables record no SUI inflow. Failed application calls rolled back, so the evidence supports spending and attempted execution—not a completed liquidation, transfer, or profit.
The gas owner is the sender itself in all 8 transactions; there is no sponsorship in this history. That identifies who paid the gas, not who operated the address.
What remains unresolved
The strongest supported description is narrow: this on-chain identity repeatedly submitted one exact two-call shape against one package revision, encountered the same liquidation abort four times, and paid substantial gas while the system could not author a meaning for the calls. Nothing in this frozen window establishes whether the attempts were manual or automated, or whether any intended economic action succeeded.
Useful exits: 2djy9hri, the representative Move abort; FeCQrBDa, a later non-failing attempt; DbqaRiK2, the congestion-canceled submission; shape b9b14bf3; and revision 0xdfba30638e09733001822640b81772ddc9362c187c1a19f7a9901f385dfdcaf9.