← previous blocknext block →recent activity
Analyzing
Block #110,329,110
25 transactions · 24 stateful · 2026-10-04 00:57:26 UTC
Parallelism
68/100
Blocked
67%
Avg conflicts / tx
2.12
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #110,329,110 · 25 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
1w02w13w24w35w46w57w68w719w224w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf35e0af3…22cf
0xd32edf…ff58
15 touches
28 conflicts
0x00000000…0013
0x1b6862…e19c
14 touches
21 conflicts
0x00000000…0015
0x1b6862…e19c
14 touches
21 conflicts
0x2ce2d49e…d186
0x1b6862…e19c
14 touches
21 conflicts
0x00000000…0052
0x1b6862…e19c
12 touches
15 conflicts
0x4b1a00ef…9007
0x1b6862…e19c
12 touches
15 conflicts
0x615d7983…1e50
0x1b6862…e19c
12 touches
15 conflicts
0x00000000…0012
0x1b6862…e19c
12 touches
15 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
28 conflicts on slot 0xf35e0af396…8322cf
Audit this contract →
← previous block·next block →recent activity