← previous blocknext block →recent activity
Analyzing
Block #86,617,137
45 transactions · 28 stateful · 2026-07-09 11:48:11 UTC
Parallelism
76/100
Blocked
61%
Avg conflicts / tx
0.98
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #86,617,137 · 45 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w15w26w37w48w59w610w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x60d3232c…6b18
0xd32edf…ff58
15 touches
28 conflicts
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0xce827910…ff22
0x065c9d…c394
6 touches
3 conflicts
0x6af306bb…2e81
0x3bd359…433a
6 touches
3 conflicts
0x1c354dc0…96de
0x754704…b603
6 touches
3 conflicts
0xf91b744e…9117
0x754704…b603
6 touches
3 conflicts
0x00000000…0012
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0013
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
28 conflicts on slot 0x60d3232c01…316b18
Audit this contract →
← previous block·next block →recent activity