← previous blocknext block →recent activity
Analyzing
Block #83,201,980
30 transactions · 24 stateful · 2026-06-23 16:08:23 UTC
Parallelism
80/100
Blocked
58%
Avg conflicts / tx
1.03
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #83,201,980 · 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
1w02w13w24w35w06w17w08w09w410w111w417w518w222w225w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcbadcd8f…ed47
0xd32edf…ff58
9 touches
10 conflicts
0x731e6d82…2883
0x065c9d…c394
8 touches
6 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
0xffc2f21e…b393
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…002a
0x1b6862…e19c
8 touches
6 conflicts
0x4979282b…2933
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
10 conflicts on slot 0xcbadcd8fd5…c1ed47
Audit this contract →
← previous block·next block →recent activity