← previous blocknext block →recent activity
Analyzing
Block #106,193,183
22 transactions · 20 stateful · 2026-09-19 13:49:16 UTC
Parallelism
59/100
Blocked
60%
Avg conflicts / tx
2
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #106,193,183 · 22 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w15w26w37w48w59w610w718w820w121w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd62f3741…b903
0x34b655…2a6f
18 touches
36 conflicts
0x9340c766…3a52
0x34b655…2a6f
12 touches
15 conflicts
0x70986451…c6bd
0x34b655…2a6f
10 touches
10 conflicts
0x3fa1fac4…826c
0x34b655…2a6f
10 touches
10 conflicts
0xfb1d5846…56af
0x34b655…2a6f
8 touches
6 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
8 touches
6 conflicts
0x1b25f260…c429
0x34b655…2a6f
8 touches
6 conflicts
0x7b713a9f…c0be
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
36 conflicts on slot 0xd62f374157…55b903
Audit this contract →
← previous block·next block →recent activity