← previous blocknext block →recent activity
Analyzing
Block #110,386,552
16 transactions · 15 stateful · 2026-10-04 05:46:25 UTC
Parallelism
63/100
Blocked
53%
Avg conflicts / tx
1.31
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #110,386,552 · 16 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w47w08w19w310w013w415w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xeeb6624f…6aa9
0xd32edf…ff58
9 touches
10 conflicts
0x00000000…0013
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…001a
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…002a
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0040
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0053
0x1b6862…e19c
6 touches
3 conflicts
0x063eca74…c2e2
0x1b6862…e19c
6 touches
3 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 0xeeb6624fa3…326aa9
Audit this contract →
← previous block·next block →recent activity