← previous blocknext block →recent activity
Analyzing
Block #106,950,123
33 transactions · 30 stateful · 2026-09-22 05:20:01 UTC
Parallelism
82/100
Blocked
50%
Avg conflicts / tx
1
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #106,950,123 · 33 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
1w03w14w25w37w010w011w212w315w016w117w118w019w221w226w328w329w430w532w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x37e40b32…c169
0x34b655…2a6f
10 touches
10 conflicts
0x6c464113…4810
0x34b655…2a6f
8 touches
6 conflicts
0x574628e9…dcc3
0x34b655…2a6f
8 touches
6 conflicts
0xa6a845d3…f24e
0xd32edf…ff58
7 touches
6 conflicts
0x4979282b…2936
0x1b6862…e19c
6 touches
3 conflicts
0xea79e6d3…68ad
0x34b655…2a6f
6 touches
3 conflicts
0xedfd12b0…dba4
0x34b655…2a6f
6 touches
3 conflicts
0x3f2168b4…37b5
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
10 conflicts on slot 0x37e40b32f6…06c169
Audit this contract →
← previous block·next block →recent activity