2026-07-19 · 13:01–23:37 UTC

A chain's day, minute by minute.

Every stored minute of the window, drawn to scale — and where a minute has a story, the machine wrote it up. Hover the chart; minutes with a green tick have a written chapter — click one to read it.

1,000,000 transactions across 637 minutes · tallest: 18:08 UTC with 7,350

The chapters 40 minutes have written stories — a few:

One split-and-transfer transaction accounted for 94% of the minute’s recorded SUI outflow

At 14:28:01.908 UTC, transaction `5D2Vej8pGGE5vjCDGoUfY5AfLCmu7UW69vL1DkXiu2hj` ran a compact two-step sequence: `split_coins`, then `transfer_objects`. MotiveLayer records a sender-side movement of **−1,049,146.921134328 SUI** and a separate **0.00075836 SUI** gas charge. The transfer path completed, but the evidence does not identify the beneficiary or establish why the value moved. It shows custody movement, not p…

read the chapter →

After 2,294 of 2,338 failures hit in its first 40 seconds, Sui's 18:08 minute settled into limit-order traffic

At 18:08 UTC on 19 July 2026, this frozen Sui minute compressed 7,350 eligible transactions into a near-continuous burst: the median gap was 0 ms across those 7,350 transactions, and the mean was 8.1 ms. It was also an abrupt failure event. 2,338 of 7,350 transactions failed—31.81%, versus 8.36% across the stored corpus—and the minute carried nearly 3.8 times the preceding minute's 1,924 eligible transactions.

read the chapter →

At 13:06, one route runner hit four different walls while Sui processed 2,237 transactions in a minute

At 13:06 UTC, Sui handled 2,237 eligible transactions with a median gap of 0 ms. The minute recorded 143 failures, or 6.4%—below the frozen corpus rate of 8.4%. That makes this look less like a chain-wide outage than a concentrated failure family.

read the chapter →

A huge liquidity attempt with no proven position

At 22:14 UTC, one transaction stood apart from an otherwise rapid order-maintenance minute. Digest `5jmg6tBq` prepared three supporting values, then called `pool_script_v2::open_position_with_liquidity_by_fix_coin`. The sender-boundary evidence records an outflow of **646,012.523375258 SUI** and **295,112.077669 USDC**. That SUI movement was about 158.5 times the corpus’s 99th-percentile SUI holding movement for comp…

read the chapter →

The first full minute of observation, not a code launch

The first full minute of the frozen Sui slice contained 2,034 eligible transactions between checkpoints 300444504 and 300444780. The corpus itself begins at 13:01:48.968 UTC, 11 seconds before this minute. It was an unusually compressed minute: the median gap was 0 ms, the 90th-percentile gap was 207 ms, and the longest idle period was only 441 ms. The activity came from 348 senders, with 552 transactions sponsored b…

read the chapter →

At 23:25, a single liquidity-position close recorded +646,019 SUI while the minute mostly recycled orders.

This UTC minute contained 2,032 eligible transactions, of which 2,003 carried an asserted meaning used for behavior counts. The minute was unusually orderly by failure rate: 61 transactions failed, or 3.0% of eligible activity, versus 8.36% across the frozen atlas. It was also extremely compressed in time—2,032 transactions arrived over 59.583 seconds, with a median gap of 0 ms, a 211 ms p90 gap, and only 441 ms of i…

read the chapter →

Chapters are AI-authored exploratory readings of the stored minute — every figure in them is drawn from the same records the explorer serves.

All 40 written minutes

13:02 The first full minute of observation, not a code launch 2,034 tx 13:03 A storm of order maintenance hid a 516,708-SUI position closure in one minute. 1,956 tx 13:04 A 516,708-SUI liquidity closure shared a minute with a 61-failure DeepBook loop 1,680 tx 13:05 A 23-second liquidity round trip dominated one crowded Sui minute 1,438 tx 13:06 At 13:06, one route runner hit four different walls while Sui processed 2,237 transactions in a minute 2,237 tx 13:09 The minute when repayment became the bottleneck 1,394 tx 13:10 The minute two previously unobserved route revisions hit the brakes 1,676 tx 13:12 At 13:12 UTC, four Sui routes reached a previously unobserved router revision—and left their purpose unresolved. 1,166 tx 13:25 The second hand changed direction 1,654 tx 13:28 The minute the routes hit their guardrails 1,905 tx 14:16 At 14:16, Sui’s swap routes reached repayment—and failed there. 2,430 tx 14:28 One split-and-transfer transaction accounted for 94% of the minute’s recorded SUI outflow 1,738 tx 14:29 A one-minute Sui traffic jam: 473 of 509 failures arrived in the first 20 seconds 1,969 tx 14:45 A Routine Order-Book Minute Hid a 646,429-SUI Position Close 1,649 tx 15:28 A 647,233-SUI liquidity exit landed in a minute where nearly one in five transactions failed 2,691 tx 17:01 One sender accounted for 600 failures in a 7,022-transaction Sui burst 7,022 tx 17:02 The first ten seconds of Sui’s 17:02 minute failed—then the minute recovered 5,805 tx 18:07 One position-closure attempt dwarfed a minute of order maintenance 1,924 tx 18:08 After 2,294 of 2,338 failures hit in its first 40 seconds, Sui's 18:08 minute settled into limit-order traffic 7,350 tx 19:05 A single position closure brought 646,015 SUI to the boundary of a minute dominated by order churn 1,392 tx 19:19 One address takes over the minute 1,255 tx 19:20 One address, three failure guards, and an orderbook in motion 1,286 tx 19:21 At 19:21, one address issued 523 order actions while a separate flash-loan route kept failing at repayment 1,250 tx 19:28 19:28 UTC: one address becomes the order book’s metronome 1,468 tx 19:29 One address, 500 order-management attempts 1,182 tx 19:31 One address supplied 41% of the minute while order cancellations, placements, and price updates filled 68% of its explained activity. 1,344 tx 19:34 A 400,000-SUI liquidity exit landed inside a minute where 613 of 1,601 transactions failed 1,601 tx 19:40 One address ran the order desk at 19:40 UTC 1,297 tx 19:44 A minute of concentrated order maintenance 1,343 tx 19:46 One minute, 466 order-maintenance transactions, and a 40,776-SUI outlier 1,127 tx 19:47 One address drove 466 of 1,202 transactions at 19:47 UTC—and six identical withdrawals hit the same funding wall 1,202 tx 19:53 The ten-second failure wall 2,311 tx 20:15 At 20:15:10, Sui turned a minute of swap routes into a 212-failure storm. 1,397 tx 20:45 A five-step liquidity-position close produced a 646,017 SUI sender inflow in one crowded minute 1,474 tx 20:49 At 20:49 UTC, Sui became a conveyor belt of swap attempts—and 414 of 1,771 transactions failed. 1,771 tx 21:55 Sui’s 21:55 minute saw 498 failures, including a 110-failure route cluster from one sender. 1,819 tx 22:12 One minute, one enormous position close, and 63 failed routes 2,380 tx 22:14 A huge liquidity attempt with no proven position 2,042 tx 22:15 A 646,012-SUI position exit arrived just as this minute’s failures surged 4,681 tx 23:25 At 23:25, a single liquidity-position close recorded +646,019 SUI while the minute mostly recycled orders. 2,032 tx

18:08 UTC

the storm — 7,350 transactions in one minute, the window's peak

One per minute

one address posts exactly one transaction every sixty seconds, all day — the Recorder

248,486 sponsored

a quarter of the chain runs on someone else's gas budget