← previous blocknext block →recent activity
Analyzing
Block #109,056,839
42 transactions · 39 stateful · 2026-09-29 14:12:35 UTC
Parallelism
50/100
Blocked
82%
Avg conflicts / tx
5.33
Longest chain
21 deep
Execution timeline
did this block parallelize well?
view
block #109,056,839 · 42 txs across 21 waves · depth 21
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
wave w14
wave w15
wave w16
wave w17
wave w18
wave w19
wave w20
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w47w48w510w611w712w813w914w1015w1116w1217w1319w1420w1521w1622w1723w1824w1925w2037w138w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x667074bd…ab5f
0xd32edf…ff58
37 touches
171 conflicts
0x00000000…0013
0x1b6862…e19c
24 touches
66 conflicts
0x00000000…0015
0x1b6862…e19c
24 touches
66 conflicts
0x00000000…0018
0x1b6862…e19c
24 touches
66 conflicts
0x00000000…0028
0x1b6862…e19c
24 touches
66 conflicts
0x00000000…0040
0x1b6862…e19c
24 touches
66 conflicts
0x00000000…0051
0x1b6862…e19c
24 touches
66 conflicts
0x123dafa9…c444
0x1b6862…e19c
24 touches
66 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
171 conflicts on slot 0x667074bde7…86ab5f
Audit this contract →
← previous block·next block →recent activity