← previous blocknext block →recent activity
Analyzing
Block #96,544,655
20 transactions · 20 stateful · 2026-08-16 17:04:30 UTC
Parallelism
70/100
Blocked
55%
Avg conflicts / tx
1.25
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #96,544,655 · 20 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w06w07w48w49w510w411w517w518w119w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf2b1bf26…2556
0xd32edf…ff58
11 touches
15 conflicts
0x00000000…0013
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…001d
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…002d
0x1b6862…e19c
6 touches
3 conflicts
0xd5b10148…e636
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0x28f324ed…9db7
0x34b655…2a6f
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
15 conflicts on slot 0xf2b1bf264e…e32556
Audit this contract →
← previous block·next block →recent activity