← previous blocknext block →recent activity
Analyzing
Block #110,887,522
19 transactions · 15 stateful · 2026-10-05 23:49:24 UTC
Parallelism
63/100
Blocked
47%
Avg conflicts / tx
1.16
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #110,887,522 · 19 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w617w018w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x05fb1c5a…3278
0xd32edf…ff58
13 touches
21 conflicts
0x7d4f80a4…bb17
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0013
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0040
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0055
0x1b6862…e19c
4 touches
1 conflict
0x2df68f10…0a9c
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0012
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
21 conflicts on slot 0x05fb1c5aad…ca3278
Audit this contract →
← previous block·next block →recent activity