← previous blocknext block →recent activity
Analyzing
Block #109,177,001
17 transactions · 16 stateful · 2026-09-30 00:18:15 UTC
Parallelism
47/100
Blocked
56%
Avg conflicts / tx
2.18
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #109,177,001 · 17 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
1w02w13w24w35w46w57w68w79w812w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0ecd59b0…2f69
0xd32edf…ff58
17 touches
36 conflicts
0x5825da64…560d
0x1b6862…e19c
16 touches
28 conflicts
0x00000000…0015
0x1b6862…e19c
16 touches
28 conflicts
0x00000000…001a
0x1b6862…e19c
16 touches
28 conflicts
0x00000000…002a
0x1b6862…e19c
16 touches
28 conflicts
0x00000000…0040
0x1b6862…e19c
16 touches
28 conflicts
0x00000000…0053
0x1b6862…e19c
16 touches
28 conflicts
0x738a3581…4c5b
0x1b6862…e19c
16 touches
28 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 0x0ecd59b076…942f69
Audit this contract →
← previous block·next block →recent activity