← previous blocknext block →recent activity
Analyzing
Block #96,695,680
8 transactions · 7 stateful · 2026-08-17 05:44:05 UTC
Parallelism
75/100
Blocked
14%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #96,695,680 · 8 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
2w04w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9b2d3bee…8eeb
0x34b655…2a6f
4 touches
1 conflict
0x9b2d3bee…8eec
0x34b655…2a6f
4 touches
1 conflict
0xc85f42b6…6f23
0x34b655…2a6f
4 touches
1 conflict
0x2267c64a…6a9f
0x34b655…2a6f
2 touches
0 conflicts
0x91b0f8ed…6bd6
0x34b655…2a6f
2 touches
0 conflicts
0x91b0f8ed…6bd7
0x34b655…2a6f
2 touches
0 conflicts
0x9d0d4346…de6a
0x34b655…2a6f
2 touches
0 conflicts
0x9fd0b5f8…f7f9
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 0x9b2d3bee9d…d68eeb
Audit this contract →
← previous block·next block →recent activity