← previous blocknext block →recent activity
Analyzing
Block #102,810,641
90 transactions · 52 stateful · 2026-09-07 17:16:35 UTC
Parallelism
81/100
Blocked
63%
Avg conflicts / tx
1.43
Longest chain
17 deep
Execution timeline
did this block parallelize well?
view
block #102,810,641 · 90 txs across 17 waves · depth 17
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
wave w14
wave w15
wave w16
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w05w06w07w18w111w112w013w130w031w234w137w238w345w446w258w262w364w570w484w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xae3a9ed2…7fff
0xd32edf…ff58
23 touches
66 conflicts
0x00000000…003d
0x065c9d…c394
12 touches
15 conflicts
0xfcb7b8b2…ebb3
0x065c9d…c394
10 touches
10 conflicts
0x443a3e47…f4a4
0x065c9d…c394
10 touches
10 conflicts
0xa1087a5c…66c4
0x754704…b603
10 touches
10 conflicts
0x01e7b865…6e6e
0x188d58…ea8e
8 touches
6 conflicts
0x01e7b865…6e6d
0x188d58…ea8e
8 touches
6 conflicts
0x17606ba6…1b6e
0x754704…b603
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
66 conflicts on slot 0xae3a9ed2a5…7e7fff
Audit this contract →
← previous block·next block →recent activity