← previous blocknext block →recent activity
Analyzing
Block #73,436,428
10 transactions · 8 stateful · 2026-05-09 10:08:14 UTC
Parallelism
60/100
Blocked
50%
Avg conflicts / tx
0.7
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #73,436,428 · 10 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w37w08w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x07c9e63f…2629
0xd32edf…ff58
7 touches
6 conflicts
0x046a928e…0012
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x483eaff7…a21e
0x065c9d…c394
2 touches
0 conflicts
0x6abcb20e…ed48
0x065c9d…c394
2 touches
0 conflicts
0xf537eaa0…73c8
0x065c9d…c394
2 touches
0 conflicts
0x00000000…0006
0x0a439a…0e3c
2 touches
0 conflicts
0x00000000…0008
0x0a439a…0e3c
2 touches
0 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
6 conflicts on slot 0x07c9e63fed…dc2629
Audit this contract →
← previous block·next block →recent activity