← previous blocknext block →recent activity
Analyzing
Block #86,762,240
38 transactions · 27 stateful · 2026-07-10 03:58:34 UTC
Parallelism
84/100
Blocked
37%
Avg conflicts / tx
0.5
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #86,762,240 · 38 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
2w04w05w17w08w19w210w314w116w018w019w120w229w434w536w037w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x76689d6e…c69b
0xd32edf…ff58
9 touches
10 conflicts
0x00000000…0002
0x04fdea…47d7
6 touches
3 conflicts
0xce827910…ff22
0x065c9d…c394
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x01e7b865…6e6d
0x188d58…ea8e
4 touches
1 conflict
0x01e7b865…6e6f
0x188d58…ea8e
4 touches
1 conflict
0x00000000…0012
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001a
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
10 conflicts on slot 0x76689d6e65…6dc69b
Audit this contract →
← previous block·next block →recent activity