← previous blocknext block →recent activity
Analyzing
Block #84,306,614
30 transactions · 26 stateful · 2026-06-28 18:56:34 UTC
Parallelism
80/100
Blocked
54%
Avg conflicts / tx
0.93
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #84,306,614 · 30 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w47w49w113w214w519w020w121w222w327w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdb6efa9e…60eb
0xd32edf…ff58
9 touches
10 conflicts
0xab86573c…682e
0x34b655…2a6f
8 touches
6 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…0013
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0019
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0029
0x1b6862…e19c
6 touches
3 conflicts
0x083a8763…5a79
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
10 conflicts on slot 0xdb6efa9e06…ab60eb
Audit this contract →
← previous block·next block →recent activity