← previous blocknext block →recent activity
Analyzing
Block #86,227,452
35 transactions · 31 stateful · 2026-07-07 16:22:57 UTC
Parallelism
71/100
Blocked
61%
Avg conflicts / tx
1.17
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #86,227,452 · 35 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w58w620w624w728w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x10150edb…bd2a
0xd32edf…ff58
13 touches
21 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x18cf3003…51d1
0x065c9d…c394
6 touches
3 conflicts
0xcc8faac2…c766
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…001f
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
21 conflicts on slot 0x10150edbae…64bd2a
Audit this contract →
← previous block·next block →recent activity