← previous blocknext block →recent activity
Analyzing
Block #85,140,918
49 transactions · 35 stateful · 2026-07-02 15:41:03 UTC
Parallelism
80/100
Blocked
51%
Avg conflicts / tx
1.02
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #85,140,918 · 49 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w68w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd7a9ef57…7f49
0xd32edf…ff58
15 touches
28 conflicts
0x00000000…0002
0x04fdea…47d7
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x731e6d82…2883
0x065c9d…c394
6 touches
3 conflicts
0x6bdb9869…7558
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x00000000…0019
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0029
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
28 conflicts on slot 0xd7a9ef571d…177f49
Audit this contract →
← previous block·next block →recent activity