← previous blocknext block →recent activity
Analyzing
Block #109,170,185
27 transactions · 25 stateful · 2026-09-29 23:43:57 UTC
Parallelism
67/100
Blocked
68%
Avg conflicts / tx
2.26
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #109,170,185 · 27 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
1w02w13w24w35w46w57w68w717w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd0c6cb35…e930
0xd32edf…ff58
15 touches
28 conflicts
0x00000000…0012
0x1b6862…e19c
14 touches
21 conflicts
0x00000000…0013
0x1b6862…e19c
14 touches
21 conflicts
0x00000000…0015
0x1b6862…e19c
14 touches
21 conflicts
0x00000000…001a
0x1b6862…e19c
14 touches
21 conflicts
0x00000000…002a
0x1b6862…e19c
14 touches
21 conflicts
0x57d3b231…a40e
0x1b6862…e19c
14 touches
21 conflicts
0x00000000…0053
0x1b6862…e19c
14 touches
21 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
28 conflicts on slot 0xd0c6cb35f8…1fe930
Audit this contract →
← previous block·next block →recent activity