← previous blocknext block →recent activity
Analyzing
Block #86,102,461
22 transactions · 18 stateful · 2026-07-07 02:28:29 UTC
Parallelism
77/100
Blocked
28%
Avg conflicts / tx
0.5
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,102,461 · 22 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w310w011w115w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6c46a05d…d9ec
0xd32edf…ff58
9 touches
10 conflicts
0xe4af4c87…9964
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x9a5f7a9b…d3d5
0x065c9d…c394
2 touches
0 conflicts
0x00000000…0012
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…0013
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…0015
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…001c
0x1b6862…e19c
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
10 conflicts on slot 0x6c46a05d05…60d9ec
Audit this contract →
← previous block·next block →recent activity