← previous blocknext block →recent activity
Analyzing
Block #73,030,019
16 transactions · 15 stateful · 2026-05-07 13:04:19 UTC
Parallelism
56/100
Blocked
47%
Avg conflicts / tx
1.19
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #73,030,019 · 16 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w411w412w513w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb4cc32bd…f4d8
0xd32edf…ff58
9 touches
10 conflicts
0x00000000…002f
0x1b6862…e19c
8 touches
6 conflicts
0x17ca7036…1e1b
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0xbd7e37a9…9eb5
0x065c9d…c394
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0012
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0013
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
10 conflicts on slot 0xb4cc32bda7…35f4d8
Audit this contract →
← previous block·next block →recent activity