← previous blocknext block →recent activity
Analyzing
Block #106,403,250
17 transactions · 17 stateful · 2026-09-20 07:26:32 UTC
Parallelism
76/100
Blocked
29%
Avg conflicts / tx
0.53
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #106,403,250 · 17 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
1w07w010w111w212w213w315w016w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcc9bc5e3…f916
0x34b655…2a6f
6 touches
3 conflicts
0xfdd131fa…dbdb
0x34b655…2a6f
4 touches
1 conflict
0xbaf6ed88…c179
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xc8e54058…6a98
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x0505bae8…b4fb
0x34b655…2a6f
4 touches
1 conflict
0x109d8a52…a7b7
0x34b655…2a6f
4 touches
1 conflict
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
3 conflicts on slot 0xcc9bc5e35b…edf916
Audit this contract →
← previous block·next block →recent activity