← previous blocknext block →recent activity
Analyzing
Block #86,565,281
41 transactions · 34 stateful · 2026-07-09 06:00:35 UTC
Parallelism
78/100
Blocked
59%
Avg conflicts / tx
1.46
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #86,565,281 · 41 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w58w211w613w614w727w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2832522f…2122
0xd32edf…ff58
17 touches
36 conflicts
0xce827910…ff22
0x065c9d…c394
10 touches
10 conflicts
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0x52e69143…95ad
0x065c9d…c394
6 touches
3 conflicts
0x00000000…0013
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…001e
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…002e
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
36 conflicts on slot 0x2832522fb2…7d2122
Audit this contract →
← previous block·next block →recent activity