← previous blocknext block →recent activity
Analyzing
Block #96,364,085
14 transactions · 13 stateful · 2026-08-16 01:56:01 UTC
Parallelism
71/100
Blocked
38%
Avg conflicts / tx
0.57
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #96,364,085 · 14 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
1w02w15w06w07w18w29w311w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x79d420e6…e576
0x968279…9342
8 touches
6 conflicts
0x79d420e6…e577
0x968279…9342
8 touches
6 conflicts
0x79d420e6…e57a
0x968279…9342
8 touches
6 conflicts
0x79d420e6…e57b
0x968279…9342
8 touches
6 conflicts
0x79d420e6…e57d
0x968279…9342
8 touches
6 conflicts
0x087c13de…7282
0x968279…9342
8 touches
6 conflicts
0x087c13de…7284
0x968279…9342
8 touches
6 conflicts
0x177211e2…1c2d
0x754704…b603
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 0x79d420e6ec…74e576
Audit this contract →
← previous block·next block →recent activity