← previous blocknext block →recent activity
Analyzing
Block #108,961,566
18 transactions · 18 stateful · 2026-09-29 06:11:11 UTC
Parallelism
50/100
Blocked
67%
Avg conflicts / tx
1.44
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #108,961,566 · 18 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
1w02w13w24w35w46w07w18w59w410w512w613w714w015w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x66f56868…948e
0xd32edf…ff58
9 touches
10 conflicts
0x00000000…0013
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…001e
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…002e
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0040
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0057
0x1b6862…e19c
6 touches
3 conflicts
0x58e06bab…34d1
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 0x66f568683a…da948e
Audit this contract →
← previous block·next block →recent activity