← previous blocknext block →recent activity
Analyzing
Block #84,120,711
36 transactions · 31 stateful · 2026-06-27 22:18:23 UTC
Parallelism
83/100
Blocked
58%
Avg conflicts / tx
1
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #84,120,711 · 36 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
1w02w13w24w35w410w011w112w213w315w523w324w126w327w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb33ff262…4cfd
0xd32edf…ff58
11 touches
15 conflicts
0x00000000…0013
0x1b6862…e19c
10 touches
10 conflicts
0xe5060fe3…ebe8
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0015
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0002
0xd637b3…4160
8 touches
6 conflicts
0x00000000…0012
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…001d
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…002d
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
15 conflicts on slot 0xb33ff26222…e04cfd
Audit this contract →
← previous block·next block →recent activity