← previous blocknext block →recent activity
Analyzing
Block #101,300,602
24 transactions · 20 stateful · 2026-09-02 10:08:53 UTC
Parallelism
63/100
Blocked
60%
Avg conflicts / tx
1.71
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #101,300,602 · 24 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w37w416w517w618w720w223w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa37f3612…0586
0xd32edf…ff58
17 touches
36 conflicts
0x00000000…001c
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…002c
0x1b6862…e19c
10 touches
10 conflicts
0x6aa624fd…a84f
0x1b6862…e19c
10 touches
10 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0012
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0013
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0015
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
36 conflicts on slot 0xa37f36124f…480586
Audit this contract →
← previous block·next block →recent activity