← previous blocknext block →recent activity
Analyzing
Block #96,180,845
10 transactions · 9 stateful · 2026-08-15 10:34:24 UTC
Parallelism
80/100
Blocked
11%
Avg conflicts / tx
0.1
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #96,180,845 · 10 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
2w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7da6eb60…b34e
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
2 touches
0 conflicts
0x0c557678…d359
0x34b655…2a6f
2 touches
0 conflicts
0x0c720bfa…407a
0x34b655…2a6f
2 touches
0 conflicts
0x1a31be72…cd74
0x34b655…2a6f
2 touches
0 conflicts
0x27412cd9…1641
0x34b655…2a6f
2 touches
0 conflicts
0x4c214bb3…c5d3
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 0x7da6eb601b…b3b34e
Audit this contract →
← previous block·next block →recent activity