← previous blocknext block →recent activity
Analyzing
Block #102,479,088
28 transactions · 20 stateful · 2026-09-06 13:19:40 UTC
Parallelism
79/100
Blocked
45%
Avg conflicts / tx
0.64
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #102,479,088 · 28 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
5w06w07w08w013w114w015w116w217w118w321w424w425w527w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x891f0af6…db6e
0xd32edf…ff58
9 touches
10 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x5f77d607…2c84
0x065c9d…c394
6 touches
3 conflicts
0x892daf6e…48d8
0x065c9d…c394
6 touches
3 conflicts
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001c
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002c
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
10 conflicts on slot 0x891f0af66c…77db6e
Audit this contract →
← previous block·next block →recent activity