← previous blocknext block →recent activity
Analyzing
Block #101,968,149
29 transactions · 23 stateful · 2026-09-04 18:10:24 UTC
Parallelism
62/100
Blocked
57%
Avg conflicts / tx
1.17
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #101,968,149 · 29 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w518w119w420w523w624w725w826w927w10
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd5ca5b03…fa58
0xd32edf…ff58
11 touches
15 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…001a
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…002a
0x1b6862…e19c
8 touches
6 conflicts
0x91220b8f…7a03
0x1b6862…e19c
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
8 touches
6 conflicts
0x326a02b5…8dad
0x34b655…2a6f
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
15 conflicts on slot 0xd5ca5b0337…c4fa58
Audit this contract →
← previous block·next block →recent activity