← previous blocknext block →recent activity
Analyzing
Block #86,795,010
28 transactions · 21 stateful · 2026-07-10 07:37:18 UTC
Parallelism
71/100
Blocked
43%
Avg conflicts / tx
1.07
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #86,795,010 · 28 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w510w615w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbc5dc9c4…9b10
0xd32edf…ff58
15 touches
28 conflicts
0x1d351a9b…f2dd
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xb4c35fcd…43ae
0xa6afd3…d132
4 touches
1 conflict
0x00000000…0013
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…0015
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…001a
0x1b6862…e19c
2 touches
0 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 0xbc5dc9c48a…7e9b10
Audit this contract →
← previous block·next block →recent activity