← previous blocknext block →recent activity
Analyzing
Block #83,863,366
63 transactions · 30 stateful · 2026-06-26 17:43:29 UTC
Parallelism
86/100
Blocked
63%
Avg conflicts / tx
0.9
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #83,863,366 · 63 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w16w27w313w414w515w618w228w253w754w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x256565d2…fae5
0xd32edf…ff58
17 touches
36 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0018
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0028
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0012
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0013
0x1b6862…e19c
8 touches
6 conflicts
0xd9f18d9a…141d
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
36 conflicts on slot 0x256565d292…70fae5
Audit this contract →
← previous block·next block →recent activity