← previous blocknext block →recent activity
Analyzing
Block #102,104,529
20 transactions · 20 stateful · 2026-09-05 05:41:48 UTC
Parallelism
55/100
Blocked
60%
Avg conflicts / tx
2.05
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #102,104,529 · 20 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
1w02w13w24w35w46w58w610w112w713w816w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdc50a040…91c7
0xd32edf…ff58
17 touches
36 conflicts
0x00000000…001c
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…002c
0x1b6862…e19c
8 touches
6 conflicts
0x93afca4c…b47c
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0012
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0013
0x1b6862…e19c
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
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 0xdc50a040b1…0e91c7
Audit this contract →
← previous block·next block →recent activity