← previous blocknext block →recent activity
Analyzing
Block #106,535,530
22 transactions · 22 stateful · 2026-09-20 18:32:20 UTC
Parallelism
64/100
Blocked
64%
Avg conflicts / tx
2.23
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #106,535,530 · 22 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
1w02w13w24w35w46w57w614w721w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xba1ac07c…7536
0xd32edf…ff58
13 touches
21 conflicts
0xb935707a…140f
0x34b655…2a6f
12 touches
15 conflicts
0xd62f3741…b903
0x34b655…2a6f
12 touches
15 conflicts
0x00000000…0015
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…001d
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…002d
0x1b6862…e19c
10 touches
10 conflicts
0x872e51c8…ae2a
0x1b6862…e19c
10 touches
10 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
10 touches
10 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
21 conflicts on slot 0xba1ac07cd8…b47536
Audit this contract →
← previous block·next block →recent activity