← previous blocknext block →recent activity
Analyzing
Block #102,479,106
23 transactions · 23 stateful · 2026-09-06 13:19:46 UTC
Parallelism
78/100
Blocked
61%
Avg conflicts / tx
1.04
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #102,479,106 · 23 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
1w02w13w24w36w18w39w010w011w112w213w314w415w016w117w118w219w321w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf89f7839…4ced
0xd32edf…ff58
9 touches
10 conflicts
0x6cb8029e…b39e
0x34b655…2a6f
6 touches
3 conflicts
0xaad6be10…0801
0x2a68ba…90c5
6 touches
3 conflicts
0x86cea35b…bdff
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001c
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002c
0x1b6862…e19c
4 touches
1 conflict
0x1da7723c…80ab
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 0xf89f7839ce…7e4ced
Audit this contract →
← previous block·next block →recent activity