← previous blocknext block →recent activity
Analyzing
Block #108,969,291
25 transactions · 22 stateful · 2026-09-29 06:50:22 UTC
Parallelism
72/100
Blocked
55%
Avg conflicts / tx
1.36
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #108,969,291 · 25 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w59w010w111w214w620w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe77a3f09…3c5c
0xd32edf…ff58
13 touches
21 conflicts
0x00000000…0057
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0015
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…001e
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…002e
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0040
0x1b6862…e19c
10 touches
10 conflicts
0x8609c77f…24f2
0x1b6862…e19c
10 touches
10 conflicts
0xc0f29314…17fd
0x1b6862…e19c
10 touches
10 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
21 conflicts on slot 0xe77a3f09e3…cd3c5c
Audit this contract →
← previous block·next block →recent activity