← previous blocknext block →recent activity
Analyzing
Block #85,214,087
19 transactions · 17 stateful · 2026-07-02 23:48:16 UTC
Parallelism
68/100
Blocked
47%
Avg conflicts / tx
0.84
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #85,214,087 · 19 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w48w09w110w013w516w217w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc7504341…e612
0xd32edf…ff58
9 touches
10 conflicts
0x6bdb9869…7558
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…001b
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002b
0x1b6862…e19c
4 touches
1 conflict
0xd4c913d7…343b
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 0xc7504341f7…80e612
Audit this contract →
← previous block·next block →recent activity