← previous blocknext block →recent activity
Analyzing
Block #108,972,293
25 transactions · 22 stateful · 2026-09-29 07:05:35 UTC
Parallelism
80/100
Blocked
36%
Avg conflicts / tx
0.8
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #108,972,293 · 25 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w49w010w111w214w018w022w023w124w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xad8e9f6c…c11f
0xd32edf…ff58
9 touches
10 conflicts
0xd6071d1d…496c
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0013
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0057
0x1b6862…e19c
6 touches
3 conflicts
0x4862f4d7…5fe1
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0012
0x1b6862…e19c
6 touches
3 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
10 conflicts on slot 0xad8e9f6c2a…86c11f
Audit this contract →
← previous block·next block →recent activity