← previous blocknext block →recent activity
Analyzing
Block #96,030,930
17 transactions · 16 stateful · 2026-08-14 22:00:18 UTC
Parallelism
76/100
Blocked
38%
Avg conflicts / tx
0.53
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #96,030,930 · 17 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w06w07w18w110w011w112w213w316w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcf3cb734…76b0
0x968279…9342
8 touches
6 conflicts
0x521a5982…a82a
0x754704…b603
8 touches
6 conflicts
0x00000000…0006
0x968279…9342
8 touches
6 conflicts
0xa2fc1825…1aef
0x968279…9342
8 touches
6 conflicts
0xa2fc1825…1af0
0x968279…9342
8 touches
6 conflicts
0xa2fc1825…1af3
0x968279…9342
8 touches
6 conflicts
0xa2fc1825…1af4
0x968279…9342
8 touches
6 conflicts
0xa2fc1825…1af6
0x968279…9342
8 touches
6 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
6 conflicts on slot 0xcf3cb734b9…3676b0
Audit this contract →
← previous block·next block →recent activity