← previous blocknext block →recent activity
Analyzing
Block #86,665,391
33 transactions · 26 stateful · 2026-07-09 17:11:46 UTC
Parallelism
91/100
Blocked
19%
Avg conflicts / tx
0.18
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,665,391 · 33 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w123w224w025w126w230w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x518d5ea8…3b5e
0xd32edf…ff58
5 touches
3 conflicts
0xce827910…ff22
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…0018
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0028
0x1b6862…e19c
4 touches
1 conflict
0x14d1bf0e…e099
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
3 conflicts on slot 0x518d5ea810…783b5e
Audit this contract →
← previous block·next block →recent activity