← previous blocknext block →recent activity
Analyzing
Block #106,565,618
33 transactions · 25 stateful · 2026-09-20 21:03:45 UTC
Parallelism
67/100
Blocked
52%
Avg conflicts / tx
1.76
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #106,565,618 · 33 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
1w02w112w113w214w315w416w517w618w720w821w823w925w227w10
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc65f46dd…513c
0x34b655…2a6f
18 touches
36 conflicts
0xe5389792…da27
0xd32edf…ff58
17 touches
36 conflicts
0xcb45d9d6…cb86
0x1b6862…e19c
16 touches
28 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
16 touches
28 conflicts
0xc102b2b7…57a2
0x34b655…2a6f
16 touches
28 conflicts
0x00000000…001e
0x1b6862…e19c
16 touches
28 conflicts
0xca841faa…486a
0x34b655…2a6f
16 touches
28 conflicts
0xcf94604f…25e6
0x34b655…2a6f
16 touches
28 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 0xc65f46dd9f…6d513c
Audit this contract →
← previous block·next block →recent activity