← previous blocknext block →recent activity
Analyzing
Block #86,715,238
34 transactions · 22 stateful · 2026-07-09 22:44:28 UTC
Parallelism
82/100
Blocked
41%
Avg conflicts / tx
0.62
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #86,715,238 · 34 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
1w02w13w29w310w419w020w523w024w125w326w432w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x66fa24fd…e62f
0xd32edf…ff58
11 touches
15 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x3e77980f…7a9c
0x065c9d…c394
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…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
15 conflicts on slot 0x66fa24fd8d…e5e62f
Audit this contract →
← previous block·next block →recent activity