← previous blocknext block →recent activity
Analyzing
Block #85,990,695
34 transactions · 28 stateful · 2026-07-06 14:02:25 UTC
Parallelism
85/100
Blocked
39%
Avg conflicts / tx
0.53
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #85,990,695 · 34 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w410w211w012w113w014w124w025w326w330w131w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xffdc196d…f2ea
0xd32edf…ff58
9 touches
10 conflicts
0xa7013be2…c0a8
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0012
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001a
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002a
0x1b6862…e19c
4 touches
1 conflict
0x48a29a03…c437
0x1b6862…e19c
4 touches
1 conflict
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
10 conflicts on slot 0xffdc196d86…e5f2ea
Audit this contract →
← previous block·next block →recent activity