← previous blocknext block →recent activity
Analyzing
Block #108,965,033
24 transactions · 15 stateful · 2026-09-29 06:28:51 UTC
Parallelism
67/100
Blocked
67%
Avg conflicts / tx
1.38
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #108,965,033 · 24 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
1w02w13w24w35w46w511w416w618w719w320w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x02007f58…13f6
0xd32edf…ff58
15 touches
28 conflicts
0x00000000…0013
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0015
0x1b6862…e19c
10 touches
10 conflicts
0x17a7f697…dcb7
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0057
0x1b6862…e19c
8 touches
6 conflicts
0x57d3b231…a412
0x1b6862…e19c
8 touches
6 conflicts
0xb8394f3d…8f29
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0012
0x1b6862…e19c
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
28 conflicts on slot 0x02007f5816…fd13f6
Audit this contract →
← previous block·next block →recent activity