← previous blocknext block →recent activity
Analyzing
Block #95,405,612
22 transactions · 21 stateful · 2026-08-12 17:33:02 UTC
Parallelism
86/100
Blocked
33%
Avg conflicts / tx
0.41
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #95,405,612 · 22 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w05w06w110w111w012w113w214w220w121w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa4756d36…e7b0
0x968279…9342
6 touches
3 conflicts
0xa4756d36…e7b1
0x968279…9342
6 touches
3 conflicts
0xa4756d36…e7b2
0x968279…9342
6 touches
3 conflicts
0xc578b023…58e5
0x968279…9342
6 touches
3 conflicts
0xc578b023…58e6
0x968279…9342
6 touches
3 conflicts
0xc578b023…58e8
0x968279…9342
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x177211e2…1c2d
0x754704…b603
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 0xa4756d3652…9ee7b0
Audit this contract →
← previous block·next block →recent activity