← previous blocknext block →recent activity
Analyzing
Block #85,643,556
23 transactions · 18 stateful · 2026-07-04 23:28:16 UTC
Parallelism
74/100
Blocked
39%
Avg conflicts / tx
0.74
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #85,643,556 · 23 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
1w02w13w24w35w48w219w020w121w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x852096a5…6212
0xd32edf…ff58
11 touches
15 conflicts
0x4546ebad…b908
0x34b655…2a6f
4 touches
1 conflict
0x9a291a56…9a9c
0x34b655…2a6f
4 touches
1 conflict
0xa2c9330e…e167
0x34b655…2a6f
4 touches
1 conflict
0xac206e47…ef7d
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xcccde2ca…b120
0x065c9d…c394
3 touches
1 conflict
0x5ffc25fa…b119
0x34b655…2a6f
3 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
15 conflicts on slot 0x852096a56d…296212
Audit this contract →
← previous block·next block →recent activity