← previous blocknext block →recent activity
Analyzing
Block #96,255,623
11 transactions · 9 stateful · 2026-08-15 16:50:30 UTC
Parallelism
64/100
Blocked
33%
Avg conflicts / tx
0.64
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #96,255,623 · 11 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
3w06w07w18w29w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfe708efe…df34
0x34b655…2a6f
6 touches
3 conflicts
0x00e2c296…0001
0x34b655…2a6f
6 touches
3 conflicts
0x0eaa3f4e…2992
0x34b655…2a6f
6 touches
3 conflicts
0x66bdb4c2…7ea6
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xdfaadc7d…ca02
0x34b655…2a6f
4 touches
1 conflict
0xf921b363…1625
0x34b655…2a6f
4 touches
1 conflict
0x2ffa0115…ed47
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 0xfe708efe93…b8df34
Audit this contract →
← previous block·next block →recent activity