← previous blocknext block →recent activity
Analyzing
Block #96,443,365
11 transactions · 8 stateful · 2026-08-16 08:34:43 UTC
Parallelism
64/100
Blocked
38%
Avg conflicts / tx
0.55
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #96,443,365 · 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
6w07w18w29w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x135f48c1…3430
0x968279…9342
8 touches
6 conflicts
0x135f48c1…3431
0x968279…9342
8 touches
6 conflicts
0x135f48c1…3434
0x968279…9342
8 touches
6 conflicts
0x135f48c1…3435
0x968279…9342
8 touches
6 conflicts
0x135f48c1…3436
0x968279…9342
8 touches
6 conflicts
0xc2f59d24…00f6
0x968279…9342
8 touches
6 conflicts
0xc2f59d24…00f7
0x968279…9342
8 touches
6 conflicts
0xc2f59d24…00f9
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 0x135f48c1b9…8d3430
Audit this contract →
← previous block·next block →recent activity