← previous blocknext block →recent activity
Analyzing
Block #84,027,913
24 transactions · 22 stateful · 2026-06-27 12:00:08 UTC
Parallelism
67/100
Blocked
41%
Avg conflicts / tx
1.33
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #84,027,913 · 24 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
1w02w13w24w35w47w08w59w618w719w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc4d2c596…9782
0xd32edf…ff58
11 touches
15 conflicts
0x0b16149e…7d4d
0x065c9d…c394
10 touches
10 conflicts
0xff96dc9b…93d7
0x065c9d…c394
10 touches
10 conflicts
0x00000000…003d
0x065c9d…c394
10 touches
10 conflicts
0x00000000…0013
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…001b
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…002b
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
15 conflicts on slot 0xc4d2c596fd…439782
Audit this contract →
← previous block·next block →recent activity