← previous blocknext block →recent activity
Analyzing
Block #106,809,595
20 transactions · 17 stateful · 2026-09-21 17:32:41 UTC
Parallelism
70/100
Blocked
35%
Avg conflicts / tx
0.85
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #106,809,595 · 20 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w05w08w19w212w313w414w517w018w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfcc8f826…7c5f
0x34b655…2a6f
8 touches
6 conflicts
0xcffc17bc…3544
0x34b655…2a6f
8 touches
6 conflicts
0x68ace5c6…d0e5
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xf90c6521…d8f0
0x34b655…2a6f
6 touches
3 conflicts
0x51087f5a…61f7
0x34b655…2a6f
6 touches
3 conflicts
0x76e2f2de…235e
0x34b655…2a6f
6 touches
3 conflicts
0x01f19c33…170d
0x34b655…2a6f
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: Perpl
6 conflicts on slot 0xfcc8f826d7…5f7c5f
Audit this contract →
← previous block·next block →recent activity