← previous blocknext block →recent activity
Analyzing
Block #95,720,939
14 transactions · 11 stateful · 2026-08-13 20:00:40 UTC
Parallelism
79/100
Blocked
36%
Avg conflicts / tx
0.43
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #95,720,939 · 14 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
4w07w08w19w210w111w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfddf16c6…4ced
0x968279…9342
6 touches
3 conflicts
0xa49a8ead…c1a7
0x968279…9342
6 touches
3 conflicts
0xa49a8ead…c1a9
0x968279…9342
6 touches
3 conflicts
0xfddf16c6…4ce6
0x968279…9342
6 touches
3 conflicts
0xfddf16c6…4ce7
0x968279…9342
6 touches
3 conflicts
0xfddf16c6…4cea
0x968279…9342
6 touches
3 conflicts
0xfddf16c6…4ceb
0x968279…9342
6 touches
3 conflicts
0x398c0e99…196a
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: 0x96827978…f09342
3 conflicts on slot 0xfddf16c691…324ced
Audit this contract →
← previous block·next block →recent activity