← previous blocknext block →recent activity
Analyzing
Block #96,784,348
16 transactions · 11 stateful · 2026-08-17 13:10:03 UTC
Parallelism
56/100
Blocked
64%
Avg conflicts / tx
0.94
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #96,784,348 · 16 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w29w310w411w112w513w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf509a8c6…0ab1
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x8ec95f2b…f4d7
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0xe8eae8a3…bacc
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xc09c3422…3c8b
0x34b655…2a6f
4 touches
1 conflict
0xcd6caad2…7929
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
10 conflicts on slot 0xf509a8c6cd…9b0ab1
Audit this contract →
← previous block·next block →recent activity