← previous blocknext block →recent activity
Analyzing
Block #83,952,711
25 transactions · 19 stateful · 2026-06-27 03:39:06 UTC
Parallelism
68/100
Blocked
53%
Avg conflicts / tx
1.16
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #83,952,711 · 25 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w611w216w622w723w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x786653cf…7a5b
0xd32edf…ff58
13 touches
21 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xff96dc9b…93d7
0x065c9d…c394
6 touches
3 conflicts
0x74424c6b…6057
0x065c9d…c394
4 touches
1 conflict
0x0b16149e…7d4d
0x065c9d…c394
4 touches
1 conflict
0x00000000…0012
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
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 0x786653cf0b…ec7a5b
Audit this contract →
← previous block·next block →recent activity