← previous blocknext block →recent activity
Analyzing
Block #95,717,567
20 transactions · 19 stateful · 2026-08-13 19:43:43 UTC
Parallelism
75/100
Blocked
47%
Avg conflicts / tx
0.65
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #95,717,567 · 20 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
2w03w14w05w17w28w29w310w414w015w116w219w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x899eaaf7…f5e5
0x968279…9342
6 touches
3 conflicts
0x00000000…0006
0x968279…9342
6 touches
3 conflicts
0x67deea80…84c3
0x968279…9342
6 touches
3 conflicts
0x67deea80…84c4
0x968279…9342
6 touches
3 conflicts
0x67deea80…84c7
0x968279…9342
6 touches
3 conflicts
0x67deea80…84c8
0x968279…9342
6 touches
3 conflicts
0x67deea80…84c9
0x968279…9342
6 touches
3 conflicts
0x899eaaf7…f5e2
0x968279…9342
6 touches
3 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: 0x96827978…f09342
3 conflicts on slot 0x899eaaf77f…81f5e5
Audit this contract →
← previous block·next block →recent activity