← previous blocknext block →recent activity
Analyzing
Block #102,406,932
39 transactions · 20 stateful · 2026-09-06 07:14:07 UTC
Parallelism
87/100
Blocked
55%
Avg conflicts / tx
0.59
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #102,406,932 · 39 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w16w27w310w011w113w321w231w032w033w435w236w137w238w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x18373d4c…cacc
0xd32edf…ff58
9 touches
10 conflicts
0xd5a25205…645a
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0013
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0xaad6be10…0801
0x2a68ba…90c5
6 touches
3 conflicts
0x00000000…0012
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…001b
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…002b
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 0x18373d4c8f…48cacc
Audit this contract →
← previous block·next block →recent activity