← previous blocknext block →recent activity
Analyzing
Block #101,306,204
37 transactions · 33 stateful · 2026-09-02 10:37:05 UTC
Parallelism
70/100
Blocked
61%
Avg conflicts / tx
1.43
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #101,306,204 · 37 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
1w02w13w24w35w46w57w520w627w630w636w10
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22867876…6306
0xd32edf…ff58
13 touches
21 conflicts
0x00000000…0012
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0013
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…001d
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…002d
0x1b6862…e19c
8 touches
6 conflicts
0x4979282b…2936
0x1b6862…e19c
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
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
21 conflicts on slot 0x228678763a…d36306
Audit this contract →
← previous block·next block →recent activity