← previous blocknext block →recent activity
Analyzing
Block #102,485,444
20 transactions · 17 stateful · 2026-09-06 13:51:53 UTC
Parallelism
70/100
Blocked
65%
Avg conflicts / tx
0.9
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #102,485,444 · 20 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
1w02w13w24w16w28w310w312w013w314w415w417w518w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x526249c5…f724
0xd32edf…ff58
9 touches
10 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…001c
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…002c
0x1b6862…e19c
6 touches
3 conflicts
0x98067f20…59e7
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0012
0x1b6862…e19c
6 touches
3 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
10 conflicts on slot 0x526249c519…57f724
Audit this contract →
← previous block·next block →recent activity