← previous blocknext block →recent activity
Analyzing
Block #106,535,094
25 transactions · 21 stateful · 2026-09-20 18:30:08 UTC
Parallelism
56/100
Blocked
57%
Avg conflicts / tx
2.6
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #106,535,094 · 25 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w08w19w210w114w315w416w517w618w719w820w921w10
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcdc81195…034d
0x34b655…2a6f
22 touches
55 conflicts
0x07c47b1c…93c8
0x34b655…2a6f
18 touches
36 conflicts
0xc824469a…6425
0x34b655…2a6f
16 touches
28 conflicts
0xfcc8f826…7c5f
0x34b655…2a6f
14 touches
21 conflicts
0xac0b4a08…faae
0x34b655…2a6f
12 touches
15 conflicts
0xe283e878…7262
0x34b655…2a6f
12 touches
15 conflicts
0x9a74ca82…17d1
0x34b655…2a6f
8 touches
6 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
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: Perpl
55 conflicts on slot 0xcdc8119530…c3034d
Audit this contract →
← previous block·next block →recent activity