← previous blocknext block →recent activity
Analyzing
Block #96,262,133
9 transactions · 9 stateful · 2026-08-15 17:23:15 UTC
Parallelism
67/100
Blocked
22%
Avg conflicts / tx
0.44
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #96,262,133 · 9 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
2w06w07w18w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x66bdb4c2…7ea6
0x34b655…2a6f
6 touches
3 conflicts
0x6b17f7a0…af41
0x34b655…2a6f
4 touches
1 conflict
0xff196840…a453
0x34b655…2a6f
4 touches
1 conflict
0x1d778644…7bb9
0x34b655…2a6f
4 touches
1 conflict
0x45abe327…abda
0x34b655…2a6f
2 touches
0 conflicts
0x56153262…21ce
0x34b655…2a6f
2 touches
0 conflicts
0x57528477…786d
0x34b655…2a6f
2 touches
0 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: Perpl
3 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity