← previous blocknext block →recent activity
Analyzing
Block #95,540,219
19 transactions · 17 stateful · 2026-08-13 04:50:38 UTC
Parallelism
68/100
Blocked
41%
Avg conflicts / tx
0.89
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #95,540,219 · 19 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w08w19w010w111w212w313w414w518w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc306e51e…a103
0x968279…9342
12 touches
15 conflicts
0x521a5982…a82a
0x754704…b603
12 touches
15 conflicts
0x00000000…0006
0x968279…9342
12 touches
15 conflicts
0x2a54175b…5249
0x968279…9342
12 touches
15 conflicts
0x2a54175b…524a
0x968279…9342
12 touches
15 conflicts
0x2a54175b…524d
0x968279…9342
12 touches
15 conflicts
0x2a54175b…524e
0x968279…9342
12 touches
15 conflicts
0x2a54175b…5250
0x968279…9342
12 touches
15 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
15 conflicts on slot 0xc306e51e0b…31a103
Audit this contract →
← previous block·next block →recent activity