← previous blocknext block →recent activity
Analyzing
Block #86,814,187
44 transactions · 35 stateful · 2026-07-10 09:45:28 UTC
Parallelism
77/100
Blocked
51%
Avg conflicts / tx
1.11
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #86,814,187 · 44 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w15w26w37w48w59w611w713w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x86865a85…d7d4
0xd32edf…ff58
17 touches
36 conflicts
0x00000000…0013
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0015
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…001b
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…002b
0x1b6862…e19c
10 touches
10 conflicts
0x45b67460…28a8
0x1b6862…e19c
10 touches
10 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0012
0x1b6862…e19c
10 touches
10 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 0x86865a856d…e8d7d4
Audit this contract →
← previous block·next block →recent activity