← previous blocknext block →recent activity
Analyzing
Block #82,733,558
40 transactions · 31 stateful · 2026-06-21 11:57:05 UTC
Parallelism
73/100
Blocked
61%
Avg conflicts / tx
1.32
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #82,733,558 · 40 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w47w58w69w716w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x220ce470…edee
0xd32edf…ff58
15 touches
28 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 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…0019
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0029
0x1b6862…e19c
8 touches
6 conflicts
0x93afca4c…b479
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 0x220ce47022…a3edee
Audit this contract →
← previous block·next block →recent activity