← previous blocknext block →recent activity
Analyzing
Block #96,482,266
15 transactions · 12 stateful · 2026-08-16 11:50:24 UTC
Parallelism
80/100
Blocked
33%
Avg conflicts / tx
0.33
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #96,482,266 · 15 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
6w07w18w09w110w211w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe48fd442…b238
0x968279…9342
6 touches
3 conflicts
0x521a5982…a82a
0x754704…b603
6 touches
3 conflicts
0x00000000…0006
0x968279…9342
6 touches
3 conflicts
0x6e9a1888…1d5d
0x968279…9342
6 touches
3 conflicts
0x6e9a1888…1d5e
0x968279…9342
6 touches
3 conflicts
0x6e9a1888…1d60
0x968279…9342
6 touches
3 conflicts
0xe48fd442…b231
0x968279…9342
6 touches
3 conflicts
0xe48fd442…b232
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 0xe48fd442b6…6db238
Audit this contract →
← previous block·next block →recent activity