← previous blocknext block →recent activity
Analyzing
Block #86,084,083
24 transactions · 21 stateful · 2026-07-07 00:25:49 UTC
Parallelism
79/100
Blocked
29%
Avg conflicts / tx
0.5
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,084,083 · 24 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
1w02w13w24w38w19w010w115w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x77d4cc46…b084
0xd32edf…ff58
9 touches
10 conflicts
0x00000000…0002
0x04fdea…47d7
4 touches
1 conflict
0xef65bff3…7c9d
0x2a68ba…90c5
4 touches
1 conflict
0x31eabacc…5859
0xa6afd3…d132
3 touches
1 conflict
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 0x77d4cc467b…83b084
Audit this contract →
← previous block·next block →recent activity