← previous blocknext block →recent activity
Analyzing
Block #85,894,953
45 transactions · 30 stateful · 2026-07-06 03:23:44 UTC
Parallelism
80/100
Blocked
53%
Avg conflicts / tx
1.13
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #85,894,953 · 45 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w613w723w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x60669a98…09e5
0xd32edf…ff58
17 touches
36 conflicts
0xea02471d…1542
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…0013
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0018
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0028
0x1b6862…e19c
6 touches
3 conflicts
0x8b41ec8f…c2d3
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
36 conflicts on slot 0x60669a988a…5309e5
Audit this contract →
← previous block·next block →recent activity