← previous blocknext block →recent activity
Analyzing
Block #108,989,049
19 transactions · 18 stateful · 2026-09-29 08:30:15 UTC
Parallelism
58/100
Blocked
56%
Avg conflicts / tx
1.63
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #108,989,049 · 19 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
1w02w13w24w35w46w57w68w713w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xec9dcdcd…e5a1
0xd32edf…ff58
15 touches
28 conflicts
0x2dbb4a74…8312
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…001e
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…002e
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0040
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0057
0x1b6862…e19c
8 touches
6 conflicts
0x4ebae4aa…7367
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 0xec9dcdcdb5…a4e5a1
Audit this contract →
← previous block·next block →recent activity