← previous blocknext block →recent activity
Analyzing
Block #106,538,620
25 transactions · 25 stateful · 2026-09-20 18:47:53 UTC
Parallelism
64/100
Blocked
64%
Avg conflicts / tx
2.2
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #106,538,620 · 25 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
1w02w13w24w35w46w57w615w716w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdd388ef1…6004
0xd32edf…ff58
17 touches
36 conflicts
0x00000000…0013
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…001d
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…002d
0x1b6862…e19c
8 touches
6 conflicts
0xba5743c7…21c4
0x1b6862…e19c
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
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: FastLane: FastLaneAuctionHandler
36 conflicts on slot 0xdd388ef121…f46004
Audit this contract →
← previous block·next block →recent activity