← previous blocknext block →recent activity
Analyzing
Block #110,329,248
18 transactions · 18 stateful · 2026-10-04 00:58:08 UTC
Parallelism
56/100
Blocked
50%
Avg conflicts / tx
1.39
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #110,329,248 · 18 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w58w69w710w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x568d728f…8f7d
0xd32edf…ff58
11 touches
15 conflicts
0x00000000…0002
0x125f12…a50b
10 touches
10 conflicts
0xba5743c7…21c0
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…0009
0x125f12…a50b
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
15 conflicts on slot 0x568d728f18…638f7d
Audit this contract →
← previous block·next block →recent activity