← previous blocknext block →recent activity
Analyzing
Block #82,966,933
24 transactions · 20 stateful · 2026-06-22 13:56:10 UTC
Parallelism
71/100
Blocked
55%
Avg conflicts / tx
1.08
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #82,966,933 · 24 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w37w49w010w511w614w515w119w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x514e2901…fa5b
0xd32edf…ff58
11 touches
15 conflicts
0x00000000…0012
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0013
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…001e
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…002e
0x1b6862…e19c
6 touches
3 conflicts
0xd5b10148…e637
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
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
15 conflicts on slot 0x514e29016d…50fa5b
Audit this contract →
← previous block·next block →recent activity