← previous blocknext block →recent activity
Analyzing
Block #108,969,206
10 transactions · 10 stateful · 2026-09-29 06:49:56 UTC
Parallelism
50/100
Blocked
50%
Avg conflicts / tx
1.1
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #108,969,206 · 10 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
1w02w13w24w35w46w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x30e79b8d…ee8d
0xd32edf…ff58
9 touches
10 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0xd4c913d7…343e
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0013
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…002e
0x1b6862…e19c
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xba38536d…2b7d
0x065c9d…c394
4 touches
1 conflict
0x00000000…0012
0x1b6862…e19c
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
10 conflicts on slot 0x30e79b8da8…c4ee8d
Audit this contract →
← previous block·next block →recent activity