← previous blocknext block →recent activity
Analyzing
Block #96,826,101
15 transactions · 14 stateful · 2026-08-17 16:40:04 UTC
Parallelism
73/100
Blocked
36%
Avg conflicts / tx
0.87
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #96,826,101 · 15 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w04w15w07w18w210w211w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc11fd961…60fc
0x34b655…2a6f
8 touches
6 conflicts
0x57cc6fdc…518b
0x34b655…2a6f
8 touches
6 conflicts
0x60a536a6…ef7a
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x574628e9…dcc3
0x34b655…2a6f
4 touches
1 conflict
0x734ee320…caae
0x34b655…2a6f
4 touches
1 conflict
0x784eaad2…d176
0x34b655…2a6f
4 touches
1 conflict
0x784eaad2…d177
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: Perpl
6 conflicts on slot 0xc11fd961f1…ee60fc
Audit this contract →
← previous block·next block →recent activity