← previous blocknext block →recent activity
Analyzing
Block #108,020,578
66 transactions · 53 stateful · 2026-09-25 23:10:30 UTC
Parallelism
73/100
Blocked
72%
Avg conflicts / tx
3.03
Longest chain
18 deep
Execution timeline
did this block parallelize well?
view
block #108,020,578 · 66 txs across 18 waves · depth 18
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
wave w14
wave w15
wave w16
wave w17
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w16w18w09w212w113w215w216w317w418w519w620w721w822w925w330w1039w341w1144w1245w1350w1452w15
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xff633fed…67ce
0xd32edf…ff58
35 touches
153 conflicts
0x00000000…001b
0x1b6862…e19c
16 touches
28 conflicts
0xcb45d9d6…cb83
0x1b6862…e19c
16 touches
28 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
14 touches
21 conflicts
0x00000000…0012
0x1b6862…e19c
14 touches
21 conflicts
0xca841faa…486a
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0x892daf6e…48d8
0x065c9d…c394
8 touches
6 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
153 conflicts on slot 0xff633fed6d…5967ce
Audit this contract →
← previous block·next block →recent activity