← previous blocknext block →recent activity
Analyzing
Block #86,104,192
33 transactions · 24 stateful · 2026-07-07 02:40:00 UTC
Parallelism
79/100
Blocked
42%
Avg conflicts / tx
0.7
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #86,104,192 · 33 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
1w02w13w24w35w413w516w021w123w526w629w030w131w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xef5f37b0…340f
0xd32edf…ff58
11 touches
15 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xba5743c7…21c3
0x1b6862…e19c
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…001c
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…002c
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
15 conflicts on slot 0xef5f37b009…19340f
Audit this contract →
← previous block·next block →recent activity