← previous blocknext block →recent activity
Analyzing
Block #96,685,673
15 transactions · 14 stateful · 2026-08-17 04:53:45 UTC
Parallelism
67/100
Blocked
36%
Avg conflicts / tx
1.07
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #96,685,673 · 15 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
1w02w03w04w15w27w310w413w014w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4c619b7d…f4fa
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xa8cee629…332b
0x34b655…2a6f
8 touches
6 conflicts
0x5906754f…b584
0x34b655…2a6f
6 touches
3 conflicts
0xc8c615d4…5da3
0x34b655…2a6f
6 touches
3 conflicts
0xdf64e5e6…75e8
0x34b655…2a6f
6 touches
3 conflicts
0x9b2d3bee…8eeb
0x34b655…2a6f
4 touches
1 conflict
0x9b2d3bee…8eec
0x34b655…2a6f
4 touches
1 conflict
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 0x4c619b7d61…22f4fa
Audit this contract →
← previous block·next block →recent activity