← previous blocknext block →recent activity
Analyzing
Block #96,031,184
24 transactions · 22 stateful · 2026-08-14 22:01:35 UTC
Parallelism
71/100
Blocked
64%
Avg conflicts / tx
1.13
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #96,031,184 · 24 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w28w49w511w414w515w016w117w018w219w620w523w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xffdb9f01…058b
0xd32edf…ff58
11 touches
15 conflicts
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001b
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002b
0x1b6862…e19c
4 touches
1 conflict
0xd996735f…8731
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
15 conflicts on slot 0xffdb9f0157…93058b
Audit this contract →
← previous block·next block →recent activity