← previous blocknext block →recent activity
Analyzing
Block #109,004,268
19 transactions · 16 stateful · 2026-09-29 09:47:01 UTC
Parallelism
74/100
Blocked
38%
Avg conflicts / tx
0.63
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #109,004,268 · 19 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w311w312w414w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd0c19b5f…6fa6
0xd32edf…ff58
9 touches
10 conflicts
0x0a9870c4…8647
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…001e
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…002e
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0040
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0057
0x1b6862…e19c
8 touches
6 conflicts
0x69017fce…85c1
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
10 conflicts on slot 0xd0c19b5f80…626fa6
Audit this contract →
← previous block·next block →recent activity