← previous blocknext block →recent activity
Analyzing
Block #86,454,643
41 transactions · 33 stateful · 2026-07-08 17:40:28 UTC
Parallelism
81/100
Blocked
64%
Avg conflicts / tx
1.34
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #86,454,643 · 41 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w411w513w316w418w520w629w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x658765a5…6665
0xd32edf…ff58
15 touches
28 conflicts
0xb6ed530c…d450
0x34b655…2a6f
8 touches
6 conflicts
0xfaef08b1…0696
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…0013
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…001b
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…002b
0x1b6862…e19c
6 touches
3 conflicts
0xba5743c7…21c2
0x1b6862…e19c
6 touches
3 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
28 conflicts on slot 0x658765a5cc…7d6665
Audit this contract →
← previous block·next block →recent activity