← previous blocknext block →recent activity
Analyzing
Block #109,177,191
21 transactions · 15 stateful · 2026-09-30 00:19:12 UTC
Parallelism
62/100
Blocked
53%
Avg conflicts / tx
1.38
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #109,177,191 · 21 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
1w02w13w24w35w46w57w612w713w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5c1e4aa9…91e3
0xd32edf…ff58
15 touches
28 conflicts
0xb1526c23…f2b6
0x1b6862…e19c
14 touches
21 conflicts
0x00000000…0013
0x1b6862…e19c
14 touches
21 conflicts
0x00000000…0015
0x1b6862…e19c
14 touches
21 conflicts
0x00000000…0040
0x1b6862…e19c
12 touches
15 conflicts
0x00000000…0053
0x1b6862…e19c
12 touches
15 conflicts
0x48f92a13…4a07
0x1b6862…e19c
12 touches
15 conflicts
0x00000000…0012
0x1b6862…e19c
12 touches
15 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 0x5c1e4aa90c…2991e3
Audit this contract →
← previous block·next block →recent activity