← previous blocknext block →recent activity
Analyzing
Block #96,356,324
9 transactions · 9 stateful · 2026-08-16 01:16:59 UTC
Parallelism
78/100
Blocked
22%
Avg conflicts / tx
0.33
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #96,356,324 · 9 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w05w16w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x2d94ecd9…43db
0x34b655…2a6f
4 touches
1 conflict
0x3a874ce6…22d1
0x34b655…2a6f
2 touches
0 conflicts
0x6ac29cfd…136d
0x34b655…2a6f
2 touches
0 conflicts
0x705ab4ae…0162
0x34b655…2a6f
2 touches
0 conflicts
0x7906fd15…a794
0x34b655…2a6f
2 touches
0 conflicts
0x8d4c0bb9…ccd3
0x34b655…2a6f
2 touches
0 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
1 conflict on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity