← previous blocknext block →recent activity
Analyzing
Block #106,924,205
39 transactions · 37 stateful · 2026-09-22 03:09:34 UTC
Parallelism
69/100
Blocked
73%
Avg conflicts / tx
2.92
Longest chain
12 deep
Execution timeline
did this block parallelize well?
view
block #106,924,205 · 39 txs across 12 waves · depth 12
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w15w17w28w311w012w113w214w315w416w517w618w719w820w928w1030w232w136w137w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x574628e9…dcc3
0x34b655…2a6f
22 touches
55 conflicts
0xfc906557…ae7f
0x34b655…2a6f
20 touches
45 conflicts
0x4ec9ff52…e6f7
0x34b655…2a6f
20 touches
45 conflicts
0x49890ced…6f23
0x34b655…2a6f
20 touches
45 conflicts
0xfe30e7e5…4a4c
0x34b655…2a6f
18 touches
36 conflicts
0xccebf5c5…8758
0x34b655…2a6f
18 touches
36 conflicts
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
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
55 conflicts on slot 0x574628e919…e4dcc3
Audit this contract →
← previous block·next block →recent activity