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