← previous blocknext block →recent activity
Analyzing
Block #96,287,734
17 transactions · 17 stateful · 2026-08-15 19:32:01 UTC
Parallelism
65/100
Blocked
29%
Avg conflicts / tx
0.88
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #96,287,734 · 17 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
7w08w19w210w311w412w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe5d33d16…5609
0x968279…9342
12 touches
15 conflicts
0xfb8fc3d8…16b1
0x968279…9342
12 touches
15 conflicts
0xfb8fc3d8…16b2
0x968279…9342
12 touches
15 conflicts
0xfb8fc3d8…16b5
0x968279…9342
12 touches
15 conflicts
0xfb8fc3d8…16b6
0x968279…9342
12 touches
15 conflicts
0xfb8fc3d8…16b8
0x968279…9342
12 touches
15 conflicts
0x177211e2…1c2d
0x754704…b603
12 touches
15 conflicts
0x521a5982…a82a
0x754704…b603
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 0xe5d33d16df…225609
Audit this contract →
← previous block·next block →recent activity