← previous blocknext block →recent activity
Analyzing
Block #95,975,754
18 transactions · 17 stateful · 2026-08-14 17:22:39 UTC
Parallelism
67/100
Blocked
53%
Avg conflicts / tx
1.39
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #95,975,754 · 18 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
2w03w15w28w310w011w112w213w314w415w516w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf9137973…409f
0x968279…9342
12 touches
15 conflicts
0x521a5982…a82a
0x754704…b603
12 touches
15 conflicts
0x00000000…0006
0x968279…9342
12 touches
15 conflicts
0xed101d7f…8ae4
0x968279…9342
12 touches
15 conflicts
0xed101d7f…8ae5
0x968279…9342
12 touches
15 conflicts
0xed101d7f…8ae7
0x968279…9342
12 touches
15 conflicts
0xf9137973…4098
0x968279…9342
12 touches
15 conflicts
0xf9137973…4099
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 0xf913797342…fe409f
Audit this contract →
← previous block·next block →recent activity