← previous blocknext block →recent activity
Analyzing
Block #86,047,864
18 transactions · 14 stateful · 2026-07-06 20:24:23 UTC
Parallelism
72/100
Blocked
50%
Avg conflicts / tx
0.72
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,047,864 · 18 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w110w011w412w116w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2c707a58…ef3f
0xd32edf…ff58
9 touches
10 conflicts
0xa159517d…d8d0
0x1001ff…1001
4 touches
1 conflict
0xc6f1b3af…c97c
0x1001ff…1001
4 touches
1 conflict
0x00000000…0000
0x276664…5732
4 touches
1 conflict
0x00000000…0002
0x276664…5732
4 touches
1 conflict
0x00000000…0004
0x276664…5732
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xddd20e39…d524
0x34b655…2a6f
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 0x2c707a586e…19ef3f
Audit this contract →
← previous block·next block →recent activity