← previous blocknext block →recent activity
Analyzing
Block #83,868,141
21 transactions · 18 stateful · 2026-06-26 18:15:25 UTC
Parallelism
67/100
Blocked
44%
Avg conflicts / tx
0.9
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #83,868,141 · 21 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
1w02w13w24w35w46w58w115w516w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf34dc298…a686
0xd32edf…ff58
11 touches
15 conflicts
0x00000000…0012
0x1b6862…e19c
8 touches
6 conflicts
0xcb45d9d6…cb80
0x1b6862…e19c
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0018
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xf6cc7de8…0b4a
0x3bd359…433a
4 touches
1 conflict
0x00000000…0002
0x63e48b…53f2
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
15 conflicts on slot 0xf34dc298d3…6aa686
Audit this contract →
← previous block·next block →recent activity