← previous blocknext block →recent activity
Analyzing
Block #82,722,017
23 transactions · 18 stateful · 2026-06-21 10:40:00 UTC
Parallelism
70/100
Blocked
44%
Avg conflicts / tx
1.04
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #82,722,017 · 23 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
1w02w13w24w35w46w59w620w021w122w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x64fa2dfe…db02
0xd32edf…ff58
13 touches
21 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x2877f440…c2c8
0x34b655…2a6f
4 touches
1 conflict
0x23ce455e…41ae
0x34b655…2a6f
4 touches
1 conflict
0x41d3bfa5…523e
0x34b655…2a6f
4 touches
1 conflict
0x87292c3e…5e25
0x34b655…2a6f
4 touches
1 conflict
0xbc04d98e…a484
0x34b655…2a6f
4 touches
1 conflict
0xe5e7089a…fb91
0x34b655…2a6f
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
21 conflicts on slot 0x64fa2dfeac…fbdb02
Audit this contract →
← previous block·next block →recent activity