← previous blocknext block →recent activity
Analyzing
Block #86,319,563
34 transactions · 27 stateful · 2026-07-08 02:38:05 UTC
Parallelism
79/100
Blocked
41%
Avg conflicts / tx
0.65
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #86,319,563 · 34 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w38w011w114w015w416w520w021w127w128w629w231w032w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6e216f92…19d1
0xd32edf…ff58
9 touches
10 conflicts
0xcc8faac2…c766
0x065c9d…c394
6 touches
3 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0019
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0029
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
10 conflicts on slot 0x6e216f92a3…f219d1
Audit this contract →
← previous block·next block →recent activity