← previous blocknext block →recent activity
Analyzing
Block #85,966,116
30 transactions · 24 stateful · 2026-07-06 11:18:12 UTC
Parallelism
67/100
Blocked
50%
Avg conflicts / tx
1.4
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #85,966,116 · 30 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
1w02w13w24w35w46w512w613w715w616w821w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00b517a8…90d7
0xd32edf…ff58
15 touches
28 conflicts
0x92d610a6…9a40
0x2a68ba…90c5
10 touches
10 conflicts
0xd35bb5ac…3586
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…001a
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…002a
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
28 conflicts on slot 0x00b517a84d…ba90d7
Audit this contract →
← previous block·next block →recent activity