← previous blocknext block →recent activity
Analyzing
Block #96,189,830
12 transactions · 11 stateful · 2026-08-15 11:19:35 UTC
Parallelism
75/100
Blocked
36%
Avg conflicts / tx
0.58
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #96,189,830 · 12 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
1w02w14w05w07w18w210w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x66bdb4c2…7ea6
0x34b655…2a6f
6 touches
3 conflicts
0xf5ea108a…dbf6
0x34b655…2a6f
6 touches
3 conflicts
0x0b1a9431…183e
0x34b655…2a6f
4 touches
1 conflict
0x0b35df1d…7c83
0x34b655…2a6f
4 touches
1 conflict
0x1244b105…8e9c
0x34b655…2a6f
4 touches
1 conflict
0x5b3f9959…fede
0x34b655…2a6f
4 touches
1 conflict
0x6939e474…4256
0x34b655…2a6f
4 touches
1 conflict
0x6c084dcb…640c
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
3 conflicts on slot 0x66bdb4c268…a97ea6
Audit this contract →
← previous block·next block →recent activity