← previous blocknext block →recent activity
Analyzing
Block #95,299,804
22 transactions · 16 stateful · 2026-08-12 08:37:09 UTC
Parallelism
68/100
Blocked
56%
Avg conflicts / tx
1.23
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #95,299,804 · 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
1w02w13w24w35w410w011w114w515w216w317w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0b6034fd…ab16
0xd32edf…ff58
13 touches
21 conflicts
0xb56f0740…7542
0x34b655…2a6f
8 touches
6 conflicts
0x35b89cd8…5092
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x6173b2b9…9872
0x34b655…2a6f
4 touches
1 conflict
0x948836ff…59ab
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6426
0x34b655…2a6f
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
21 conflicts on slot 0x0b6034fd9b…94ab16
Audit this contract →
← previous block·next block →recent activity