← previous blocknext block →recent activity
Analyzing
Block #96,613,420
22 transactions · 19 stateful · 2026-08-16 22:50:22 UTC
Parallelism
68/100
Blocked
58%
Avg conflicts / tx
1.27
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #96,613,420 · 22 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
2w03w14w25w36w47w510w011w615w118w219w520w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfe5e29a7…5ba1
0xd32edf…ff58
13 touches
21 conflicts
0x26bb6db7…f863
0x1b6862…e19c
6 touches
3 conflicts
0x9ff176a9…152e
0x065c9d…c394
6 touches
3 conflicts
0x00000000…0012
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0013
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…001f
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…002f
0x1b6862…e19c
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
21 conflicts on slot 0xfe5e29a722…af5ba1
Audit this contract →
← previous block·next block →recent activity