← previous blocknext block →recent activity
Analyzing
Block #96,179,728
14 transactions · 10 stateful · 2026-08-15 10:28:46 UTC
Parallelism
86/100
Blocked
10%
Avg conflicts / tx
0.14
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #96,179,728 · 14 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
5w07w08w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x66bdb4c2…7ea6
0x34b655…2a6f
4 touches
1 conflict
0xc1f6acda…6abb
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x1a31be72…cd74
0x34b655…2a6f
2 touches
0 conflicts
0x22e0cc1d…ad04
0x34b655…2a6f
2 touches
0 conflicts
0x2399f0e0…f943
0x34b655…2a6f
2 touches
0 conflicts
0x4c214bb3…c5d3
0x34b655…2a6f
2 touches
0 conflicts
0x67bfbc55…7b2f
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 0x66bdb4c268…a97ea6
Audit this contract →
← previous block·next block →recent activity