← previous blocknext block →recent activity
Analyzing
Block #102,841,452
18 transactions · 18 stateful · 2026-09-07 19:51:43 UTC
Parallelism
72/100
Blocked
56%
Avg conflicts / tx
0.94
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #102,841,452 · 18 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w36w37w08w09w112w113w214w416w117w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x631db9ba…b039
0xd32edf…ff58
7 touches
6 conflicts
0x6fce7a05…d778
0x34b655…2a6f
6 touches
3 conflicts
0x443a3e47…f4a4
0x065c9d…c394
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001b
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002b
0x1b6862…e19c
4 touches
1 conflict
0xd25997d0…a686
0x1b6862…e19c
4 touches
1 conflict
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
6 conflicts on slot 0x631db9ba9c…9fb039
Audit this contract →
← previous block·next block →recent activity