← previous blocknext block →recent activity
Analyzing
Block #106,570,207
17 transactions · 16 stateful · 2026-09-20 21:26:50 UTC
Parallelism
65/100
Blocked
63%
Avg conflicts / tx
1.71
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #106,570,207 · 17 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w58w112w213w315w416w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0960c963…18e4
0xd32edf…ff58
11 touches
15 conflicts
0x20b1228b…2487
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…001e
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…002e
0x1b6862…e19c
8 touches
6 conflicts
0xc6a8c250…737f
0x1b6862…e19c
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
8 touches
6 conflicts
0x17f18fe3…94e4
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: FastLane: FastLaneAuctionHandler
15 conflicts on slot 0x0960c9630a…ed18e4
Audit this contract →
← previous block·next block →recent activity