← previous blocknext block →recent activity
Analyzing
Block #86,500,317
30 transactions · 28 stateful · 2026-07-08 22:45:52 UTC
Parallelism
73/100
Blocked
54%
Avg conflicts / tx
1.17
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #86,500,317 · 30 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
1w02w13w24w35w46w38w59w614w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3c40e6c7…2189
0xd32edf…ff58
13 touches
21 conflicts
0x00000000…0000
0xfa32f9…f3f0
6 touches
3 conflicts
0x00000000…0001
0xfa32f9…f3f0
6 touches
3 conflicts
0x8a2f9a36…fb4a
0xfa32f9…f3f0
6 touches
3 conflicts
0x00000000…0013
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…001c
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…002c
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
21 conflicts on slot 0x3c40e6c7e0…b22189
Audit this contract →
← previous block·next block →recent activity