← previous blocknext block →recent activity
Analyzing
Block #85,914,697
34 transactions · 24 stateful · 2026-07-06 05:35:16 UTC
Parallelism
68/100
Blocked
67%
Avg conflicts / tx
1.82
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #85,914,697 · 34 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w68w79w810w911w120w10
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb963e233…6005
0xd32edf…ff58
21 touches
55 conflicts
0x160f117d…8e90
0x065c9d…c394
4 touches
1 conflict
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…0019
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0029
0x1b6862…e19c
4 touches
1 conflict
0xba5743c7…21c0
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
55 conflicts on slot 0xb963e2331a…116005
Audit this contract →
← previous block·next block →recent activity