← previous blocknext block →recent activity
Analyzing
Block #96,795,631
16 transactions · 14 stateful · 2026-08-17 14:06:48 UTC
Parallelism
69/100
Blocked
29%
Avg conflicts / tx
0.75
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #96,795,631 · 16 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w15w06w210w315w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x988a4b26…82f8
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0xacd1b162…bee6
0x34b655…2a6f
6 touches
3 conflicts
0xf0e5a298…4827
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x86cea35b…bdff
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
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 0x988a4b2667…7982f8
Audit this contract →
← previous block·next block →recent activity