← previous blocknext block →recent activity
Analyzing
Block #85,929,590
30 transactions · 24 stateful · 2026-07-06 07:14:30 UTC
Parallelism
77/100
Blocked
58%
Avg conflicts / tx
1.03
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #85,929,590 · 30 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w08w310w011w114w415w520w624w425w427w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf961e35e…948d
0xd32edf…ff58
13 touches
21 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x160f117d…8e90
0x065c9d…c394
4 touches
1 conflict
0xb33ff823…1188
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
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
21 conflicts on slot 0xf961e35ed3…f2948d
Audit this contract →
← previous block·next block →recent activity