← previous blocknext block →recent activity
Analyzing
Block #86,045,333
50 transactions · 36 stateful · 2026-07-06 20:07:32 UTC
Parallelism
80/100
Blocked
58%
Avg conflicts / tx
1.06
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #86,045,333 · 50 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
2w03w14w25w36w47w58w69w215w234w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1533dbe9…c46c
0xd32edf…ff58
15 touches
28 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0x00000000…0012
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0013
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…001b
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…002b
0x1b6862…e19c
8 touches
6 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 0x1533dbe91c…aac46c
Audit this contract →
← previous block·next block →recent activity