← previous blocknext block →recent activity
Analyzing
Block #106,009,158
30 transactions · 21 stateful · 2026-09-18 22:23:09 UTC
Parallelism
77/100
Blocked
52%
Avg conflicts / tx
0.9
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #106,009,158 · 30 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w19w112w517w222w627w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xaf185b9b…ee43
0xd32edf…ff58
13 touches
21 conflicts
0xaad6be10…0801
0x2a68ba…90c5
6 touches
3 conflicts
0x00000000…0012
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001b
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002b
0x1b6862…e19c
4 touches
1 conflict
0xc2aacf41…5500
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
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
21 conflicts on slot 0xaf185b9b30…88ee43
Audit this contract →
← previous block·next block →recent activity