← previous blocknext block →recent activity
Analyzing
Block #73,374,623
24 transactions · 19 stateful · 2026-05-09 03:17:02 UTC
Parallelism
67/100
Blocked
42%
Avg conflicts / tx
1.25
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #73,374,623 · 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
1w02w13w24w35w46w57w69w623w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5b66d3c1…462e
0xd32edf…ff58
15 touches
28 conflicts
0x00000000…001e
0x1b6862…e19c
6 touches
3 conflicts
0x4d87512b…897c
0x065c9d…c394
6 touches
3 conflicts
0x00000000…0012
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0013
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…002e
0x1b6862…e19c
6 touches
3 conflicts
0x9b334941…fde0
0x1b6862…e19c
6 touches
3 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 0x5b66d3c1a9…c5462e
Audit this contract →
← previous block·next block →recent activity