← previous blocknext block →recent activity
Analyzing
Block #110,156,445
17 transactions · 16 stateful · 2026-10-03 10:28:37 UTC
Parallelism
47/100
Blocked
63%
Avg conflicts / tx
2.24
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #110,156,445 · 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
1w02w13w24w35w46w57w68w711w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4cdd5503…65f4
0xd32edf…ff58
17 touches
36 conflicts
0x792299c4…16b7
0x1b6862…e19c
16 touches
28 conflicts
0x00000000…0013
0x1b6862…e19c
16 touches
28 conflicts
0x00000000…0015
0x1b6862…e19c
16 touches
28 conflicts
0x00000000…0040
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0057
0x1b6862…e19c
10 touches
10 conflicts
0x5eb5c837…6f7e
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0012
0x1b6862…e19c
10 touches
10 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 0x4cdd5503a4…0565f4
Audit this contract →
← previous block·next block →recent activity