← previous blocknext block →recent activity
Analyzing
Block #110,379,918
18 transactions · 17 stateful · 2026-10-04 05:13:03 UTC
Parallelism
39/100
Blocked
65%
Avg conflicts / tx
3.11
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #110,379,918 · 18 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w68w79w810w911w10
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa41e7820…2d2a
0xd32edf…ff58
21 touches
55 conflicts
0x00000000…0013
0x1b6862…e19c
20 touches
45 conflicts
0xe783dfa4…5495
0x1b6862…e19c
20 touches
45 conflicts
0x00000000…0015
0x1b6862…e19c
20 touches
45 conflicts
0x00000000…002a
0x1b6862…e19c
16 touches
28 conflicts
0x00000000…0012
0x1b6862…e19c
16 touches
28 conflicts
0x00000000…001a
0x1b6862…e19c
16 touches
28 conflicts
0x00000000…0053
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
55 conflicts on slot 0xa41e782017…a62d2a
Audit this contract →
← previous block·next block →recent activity