← previous blocknext block →recent activity
Analyzing
Block #84,521,685
29 transactions · 25 stateful · 2026-06-29 18:50:21 UTC
Parallelism
86/100
Blocked
32%
Avg conflicts / tx
0.45
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #84,521,685 · 29 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w38w19w010w111w119w021w123w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7a2b1ea2…e60e
0xd32edf…ff58
7 touches
6 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0x729c91b8…9537
0x188d58…ea8e
4 touches
1 conflict
0x729c91b8…9539
0x188d58…ea8e
4 touches
1 conflict
0x00000000…0012
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001d
0x1b6862…e19c
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
6 conflicts on slot 0x7a2b1ea20a…34e60e
Audit this contract →
← previous block·next block →recent activity