← previous blocknext block →recent activity
Analyzing
Block #102,429,405
31 transactions · 22 stateful · 2026-09-06 09:08:00 UTC
Parallelism
81/100
Blocked
55%
Avg conflicts / tx
0.77
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #102,429,405 · 31 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w25w36w07w18w09w010w115w020w321w124w126w427w529w430w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x57c90f27…d7ed
0xd32edf…ff58
11 touches
15 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xb87af72a…aef6
0x2a68ba…90c5
6 touches
3 conflicts
0x362ba65b…9475
0x065c9d…c394
5 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
0xb538c6fa…9ae8
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
15 conflicts on slot 0x57c90f274f…57d7ed
Audit this contract →
← previous block·next block →recent activity