← previous blocknext block →recent activity
Analyzing
Block #96,287,728
16 transactions · 15 stateful · 2026-08-15 19:31:59 UTC
Parallelism
63/100
Blocked
47%
Avg conflicts / tx
1.13
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #96,287,728 · 16 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
2w06w07w18w19w010w111w212w313w414w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfb8fc3d8…16b8
0x968279…9342
12 touches
15 conflicts
0x521a5982…a82a
0x754704…b603
12 touches
15 conflicts
0x00000000…0006
0x968279…9342
12 touches
15 conflicts
0xe5d33d16…5606
0x968279…9342
12 touches
15 conflicts
0xe5d33d16…5607
0x968279…9342
12 touches
15 conflicts
0xe5d33d16…5609
0x968279…9342
12 touches
15 conflicts
0xfb8fc3d8…16b1
0x968279…9342
12 touches
15 conflicts
0xfb8fc3d8…16b2
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 0xfb8fc3d8c1…9116b8
Audit this contract →
← previous block·next block →recent activity