← previous blocknext block →recent activity
Analyzing
Block #103,221,356
20 transactions · 20 stateful · 2026-09-09 03:45:43 UTC
Parallelism
60/100
Blocked
65%
Avg conflicts / tx
1.8
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #103,221,356 · 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
1w02w13w24w35w46w58w19w412w613w514w315w617w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1888c89c…b86a
0xd32edf…ff58
13 touches
21 conflicts
0x00000000…0013
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0012
0x1b6862…e19c
10 touches
10 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…0015
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…001b
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…002b
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 0x1888c89c30…0bb86a
Audit this contract →
← previous block·next block →recent activity