← previous blocknext block →recent activity
Analyzing
Block #111,060,304
30 transactions · 21 stateful · 2026-10-06 14:20:39 UTC
Parallelism
80/100
Blocked
48%
Avg conflicts / tx
0.83
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #111,060,304 · 30 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
4w06w09w011w112w113w214w319w220w321w423w524w025w126w029w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x01b39c6f…fa19
0xd32edf…ff58
11 touches
15 conflicts
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0018
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0028
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0051
0x1b6862…e19c
4 touches
1 conflict
0x874cb67f…26da
0x1b6862…e19c
4 touches
1 conflict
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
15 conflicts on slot 0x01b39c6f14…aefa19
Audit this contract →
← previous block·next block →recent activity