← previous blocknext block →recent activity

Analyzing

Block #98,504,568

22 transactions · 17 stateful · 2026-08-23 14:38:56 UTC

Parallelism

77/100

Blocked

53%

Avg conflicts / tx

0.86

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #98,504,568  ·  22 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others

Conflict graph

Blocked by

- write/write- - read/write

x = tx position · y = wave (depth)

Hot storage slots

Contention

0x93e4ce2e…0412

0xd32edf…ff58

9 touches
10 conflicts

0xc824469a…6425

0x34b655…2a6f

8 touches
6 conflicts

0x7662d077…c6bc

0x34b655…2a6f

8 touches
6 conflicts

0x482471ad…122f

0x34b655…2a6f

8 touches
6 conflicts

0x00000000…001c

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…002c

0x1b6862…e19c

6 touches
3 conflicts

0x3e04662b…0da5

0x1b6862…e19c

6 touches
3 conflicts

0x889d5e90…929a

0x2a68ba…90c5

6 touches
3 conflicts

What's blocking what?

Click any transaction in the timeline or graph to see which storage slots forced it to wait, and which later transactions it blocked.

The bottleneck

Throughput-killer: FastLane: FastLaneAuctionHandler

10 conflicts on slot 0x93e4ce2e4a…3c0412

← previous block·next block →recent activity