← previous blocknext block →recent activity
Analyzing
Block #108,685,552
20 transactions · 17 stateful · 2026-09-28 06:57:48 UTC
Parallelism
55/100
Blocked
59%
Avg conflicts / tx
1.95
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #108,685,552 · 20 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w68w79w816w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x80e8a7ae…af5c
0xd32edf…ff58
17 touches
36 conflicts
0x00000000…0018
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0012
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0013
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0028
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0051
0x1b6862…e19c
6 touches
3 conflicts
0x5c421c70…c2eb
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
36 conflicts on slot 0x80e8a7ae66…c8af5c
Audit this contract →
← previous block·next block →recent activity