← previous blocknext block →recent activity
Analyzing
Block #86,978,906
23 transactions · 21 stateful · 2026-07-11 04:06:38 UTC
Parallelism
74/100
Blocked
48%
Avg conflicts / tx
1.13
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #86,978,906 · 23 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
1w02w13w24w35w06w310w414w515w016w118w219w420w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x64f9dfaf…6587
0xd32edf…ff58
11 touches
15 conflicts
0xce827910…ff22
0x065c9d…c394
6 touches
3 conflicts
0x046a928e…0012
0x2a68ba…90c5
6 touches
3 conflicts
0x034d14da…9f5f
0x34b655…2a6f
6 touches
3 conflicts
0x6b75f0c2…d323
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…001e
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002e
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 0x64f9dfaf99…106587
Audit this contract →
← previous block·next block →recent activity