← previous blocknext block →recent activity
Analyzing
Block #96,696,721
14 transactions · 11 stateful · 2026-08-17 05:49:19 UTC
Parallelism
57/100
Blocked
45%
Avg conflicts / tx
0.86
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #96,696,721 · 14 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w06w17w28w310w411w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb5924647…4cf1
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…00c9
0x34b655…2a6f
8 touches
6 conflicts
0x4acc6dca…a868
0x34b655…2a6f
8 touches
6 conflicts
0x784eaad2…d176
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…641f
0x34b655…2a6f
8 touches
6 conflicts
0xfb709ada…240f
0x34b655…2a6f
8 touches
6 conflicts
0xe5e4c9f0…5014
0x34b655…2a6f
7 touches
6 conflicts
0xea02471d…1542
0x34b655…2a6f
6 touches
3 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
10 conflicts on slot 0xb592464735…664cf1
Audit this contract →
← previous block·next block →recent activity