← previous blocknext block →recent activity
Analyzing
Block #110,386,548
22 transactions · 20 stateful · 2026-10-04 05:46:24 UTC
Parallelism
59/100
Blocked
65%
Avg conflicts / tx
1.95
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #110,386,548 · 22 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
1w02w13w24w35w46w57w68w79w818w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0d5581a0…5263
0xd32edf…ff58
17 touches
36 conflicts
0x00000000…0013
0x1b6862…e19c
16 touches
28 conflicts
0x00000000…0015
0x1b6862…e19c
16 touches
28 conflicts
0x00000000…001a
0x1b6862…e19c
16 touches
28 conflicts
0x00000000…002a
0x1b6862…e19c
16 touches
28 conflicts
0x00000000…0040
0x1b6862…e19c
16 touches
28 conflicts
0x00000000…0053
0x1b6862…e19c
16 touches
28 conflicts
0x2b093939…9085
0x1b6862…e19c
16 touches
28 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 0x0d5581a07b…745263
Audit this contract →
← previous block·next block →recent activity