← previous blocknext block →recent activity
Analyzing
Block #96,541,014
11 transactions · 9 stateful · 2026-08-16 16:46:11 UTC
Parallelism
64/100
Blocked
44%
Avg conflicts / tx
0.64
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #96,541,014 · 11 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
2w03w15w06w17w28w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcf6f8faf…b9d4
0x968279…9342
8 touches
6 conflicts
0x521a5982…a82a
0x754704…b603
8 touches
6 conflicts
0x00000000…0006
0x968279…9342
8 touches
6 conflicts
0x507c7235…0b19
0x968279…9342
8 touches
6 conflicts
0x507c7235…0b1a
0x968279…9342
8 touches
6 conflicts
0x507c7235…0b1c
0x968279…9342
8 touches
6 conflicts
0xcf6f8faf…b9cd
0x968279…9342
8 touches
6 conflicts
0xcf6f8faf…b9ce
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 0xcf6f8fafdb…80b9d4
Audit this contract →
← previous block·next block →recent activity