← previous blocknext block →recent activity
Analyzing
Block #86,943,902
22 transactions · 19 stateful · 2026-07-11 00:12:48 UTC
Parallelism
64/100
Blocked
47%
Avg conflicts / tx
0.73
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #86,943,902 · 22 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
1w02w13w24w35w47w514w015w116w618w719w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x489504d2…c44d
0xd32edf…ff58
9 touches
10 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x00000000…0012
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0013
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…001d
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…002d
0x1b6862…e19c
6 touches
3 conflicts
0x14d1bf0e…e09e
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
10 conflicts on slot 0x489504d224…f8c44d
Audit this contract →
← previous block·next block →recent activity