← previous blocknext block →recent activity
Analyzing
Block #108,603,661
14 transactions · 14 stateful · 2026-09-28 00:05:17 UTC
Parallelism
43/100
Blocked
57%
Avg conflicts / tx
2.07
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #108,603,661 · 14 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
1w02w13w24w35w46w57w68w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5b1c4c57…2347
0xd32edf…ff58
15 touches
28 conflicts
0x00000000…001e
0x1b6862…e19c
10 touches
10 conflicts
0xcb45d9d6…cb86
0x1b6862…e19c
10 touches
10 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0012
0x1b6862…e19c
10 touches
10 conflicts
0x945d1dbe…e1d7
0xc8689a…ee79
6 touches
3 conflicts
0x280aaa58…1c52
0x34b655…2a6f
4 touches
1 conflict
0x309f47c0…e1cf
0x34b655…2a6f
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
28 conflicts on slot 0x5b1c4c57a3…532347
Audit this contract →
← previous block·next block →recent activity