← previous blocknext block →recent activity
Analyzing
Block #96,158,261
10 transactions · 9 stateful · 2026-08-15 08:40:49 UTC
Parallelism
70/100
Blocked
33%
Avg conflicts / tx
0.4
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #96,158,261 · 10 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w25w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x380ee364…652f
0xd32edf…ff58
5 touches
3 conflicts
0x41469894…5990
0x34b655…2a6f
4 touches
1 conflict
0x43a02937…4672
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x41469894…598f
0x34b655…2a6f
4 touches
1 conflict
0xffc26b06…715e
0x34b655…2a6f
4 touches
1 conflict
0xffc26b06…715f
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
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
3 conflicts on slot 0x380ee36484…57652f
Audit this contract →
← previous block·next block →recent activity