← previous blocknext block →recent activity
Analyzing
Block #72,817,620
56 transactions · 35 stateful · 2026-05-06 13:30:07 UTC
Parallelism
86/100
Blocked
57%
Avg conflicts / tx
1.11
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #72,817,620 · 56 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
1w02w13w24w35w413w314w418w132w533w644w553w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x271065d4…ac68
0xd32edf…ff58
15 touches
28 conflicts
0x00000000…0012
0x1b6862…e19c
10 touches
10 conflicts
0x60f7fbaf…bd58
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…0013
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0015
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…001b
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…002b
0x1b6862…e19c
10 touches
10 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
10 touches
10 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
28 conflicts on slot 0x271065d489…c6ac68
Audit this contract →
← previous block·next block →recent activity