← previous blocknext block →recent activity
Analyzing
Block #86,735,604
23 transactions · 17 stateful · 2026-07-10 01:00:33 UTC
Parallelism
70/100
Blocked
47%
Avg conflicts / tx
1
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #86,735,604 · 23 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
1w02w13w24w35w410w114w515w616w017w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x638b51e6…db64
0xd32edf…ff58
13 touches
21 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x8e80434a…a96d
0x0555e3…2b9c
2 touches
0 conflicts
0xa4f80979…4d71
0x065c9d…c394
2 touches
0 conflicts
0xfde00f50…102a
0x065c9d…c394
2 touches
0 conflicts
0x01e7b865…6e6d
0x188d58…ea8e
2 touches
0 conflicts
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 0x638b51e6fe…0cdb64
Audit this contract →
← previous block·next block →recent activity