← previous blocknext block →recent activity
Analyzing
Block #84,512,193
40 transactions · 34 stateful · 2026-06-29 17:47:04 UTC
Parallelism
75/100
Blocked
53%
Avg conflicts / tx
1.48
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #84,512,193 · 40 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w59w111w612w713w826w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3c9084f9…7f20
0xd32edf…ff58
17 touches
36 conflicts
0x00000000…003d
0x065c9d…c394
10 touches
10 conflicts
0x00000000…002d
0x1b6862…e19c
8 touches
6 conflicts
0xff96dc9b…93d7
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
0x00000000…001d
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 0x3c9084f95f…437f20
Audit this contract →
← previous block·next block →recent activity