← previous blocknext block →recent activity
Analyzing
Block #96,604,422
20 transactions · 16 stateful · 2026-08-16 22:05:06 UTC
Parallelism
75/100
Blocked
50%
Avg conflicts / tx
0.95
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #96,604,422 · 20 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
1w03w04w16w07w19w210w313w114w416w017w219w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x0f6aef87…8137
0x34b655…2a6f
8 touches
6 conflicts
0xea90021c…a777
0x34b655…2a6f
8 touches
6 conflicts
0x4acbdbcf…a8c6
0x34b655…2a6f
8 touches
6 conflicts
0xffa7d0a4…b10a
0x40c49f…2af0
6 touches
3 conflicts
0x81681867…64fa
0x34b655…2a6f
6 touches
3 conflicts
0xfa381fa5…58cd
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
6 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity