← previous blocknext block →recent activity
Analyzing
Block #95,074,613
16 transactions · 15 stateful · 2026-08-11 13:35:05 UTC
Parallelism
81/100
Blocked
40%
Avg conflicts / tx
0.44
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #95,074,613 · 16 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
1w02w14w05w18w210w011w112w213w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0fdd76fe…2f3b
0x968279…9342
6 touches
3 conflicts
0x0fdd76fe…2f3c
0x968279…9342
6 touches
3 conflicts
0x0fdd76fe…2f3e
0x968279…9342
6 touches
3 conflicts
0x3d475ccd…84f1
0x968279…9342
6 touches
3 conflicts
0x3d475ccd…84f2
0x968279…9342
6 touches
3 conflicts
0x3d475ccd…84f5
0x968279…9342
6 touches
3 conflicts
0x3d475ccd…84f6
0x968279…9342
6 touches
3 conflicts
0x3d475ccd…84f8
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 0x0fdd76fec6…6b2f3b
Audit this contract →
← previous block·next block →recent activity