← previous blocknext block →recent activity
Analyzing
Block #95,972,597
24 transactions · 20 stateful · 2026-08-14 17:06:46 UTC
Parallelism
83/100
Blocked
50%
Avg conflicts / tx
0.71
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #95,972,597 · 24 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w25w06w09w111w212w315w016w117w218w320w021w123w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xff196840…a453
0x34b655…2a6f
8 touches
6 conflicts
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0xf2c1ee5b…9ab5
0x968279…9342
6 touches
3 conflicts
0x535d1d22…ef7a
0x968279…9342
6 touches
3 conflicts
0x535d1d22…ef7b
0x968279…9342
6 touches
3 conflicts
0xf2c1ee5b…9ab2
0x968279…9342
6 touches
3 conflicts
0xf2c1ee5b…9ab3
0x968279…9342
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
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: Perpl
6 conflicts on slot 0xff19684070…f2a453
Audit this contract →
← previous block·next block →recent activity