← previous blocknext block →recent activity
Analyzing
Block #96,609,797
9 transactions · 9 stateful · 2026-08-16 22:32:09 UTC
Parallelism
56/100
Blocked
33%
Avg conflicts / tx
1.11
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #96,609,797 · 9 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
1w02w03w04w16w27w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xda46a376…f6a6
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xc69edfa9…70e1
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xd192f4ed…d7ec
0x34b655…2a6f
6 touches
3 conflicts
0x949560b4…6916
0x34b655…2a6f
6 touches
3 conflicts
0x3226e3fe…f799
0x34b655…2a6f
4 touches
1 conflict
0x3c0e49c9…7833
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 0xda46a376d7…59f6a6
Audit this contract →
← previous block·next block →recent activity