← previous blocknext block →recent activity
Analyzing
Block #106,466,399
20 transactions · 20 stateful · 2026-09-20 12:44:24 UTC
Parallelism
60/100
Blocked
55%
Avg conflicts / tx
1.95
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #106,466,399 · 20 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w06w19w210w011w112w315w416w517w618w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xac5f3ead…0195
0x34b655…2a6f
16 touches
28 conflicts
0xb1927b58…f161
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…002c
0x1b6862…e19c
8 touches
6 conflicts
0x3e04662b…0da5
0x1b6862…e19c
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
8 touches
6 conflicts
0x2c2db8e9…fdc7
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
28 conflicts on slot 0xac5f3eadc9…b00195
Audit this contract →
← previous block·next block →recent activity