← previous blocknext block →recent activity
Analyzing
Block #98,382,794
15 transactions · 13 stateful · 2026-08-23 04:24:52 UTC
Parallelism
67/100
Blocked
69%
Avg conflicts / tx
1.13
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #98,382,794 · 15 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
1w02w16w17w28w210w211w312w413w314w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa23cf326…8f16
0xd32edf…ff58
9 touches
10 conflicts
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0x15698ac9…2a46
0x34b655…2a6f
6 touches
3 conflicts
0xba5743c7…21c1
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001a
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002a
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
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 0xa23cf3266e…b28f16
Audit this contract →
← previous block·next block →recent activity