← previous blocknext block →recent activity
Analyzing
Block #86,328,962
30 transactions · 25 stateful · 2026-07-08 03:40:49 UTC
Parallelism
77/100
Blocked
56%
Avg conflicts / tx
1.07
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #86,328,962 · 30 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w37w49w010w111w012w117w519w120w625w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9cf766c3…cace
0xd32edf…ff58
13 touches
21 conflicts
0x1da7723c…80a8
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0012
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0013
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0019
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0029
0x1b6862…e19c
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
8 touches
6 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
21 conflicts on slot 0x9cf766c38f…b2cace
Audit this contract →
← previous block·next block →recent activity