← previous blocknext block →recent activity
Analyzing
Block #73,447,040
27 transactions · 21 stateful · 2026-05-09 11:18:57 UTC
Parallelism
63/100
Blocked
57%
Avg conflicts / tx
1.48
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #73,447,040 · 27 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w05w16w010w111w212w313w417w519w620w721w822w723w824w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xed571fa6…6a38
0xd32edf…ff58
13 touches
21 conflicts
0x4d87512b…897c
0x065c9d…c394
10 touches
10 conflicts
0x00000000…003d
0x065c9d…c394
10 touches
10 conflicts
0x22e295f5…1bef
0x065c9d…c394
8 touches
6 conflicts
0x046a928e…0012
0x2a68ba…90c5
6 touches
3 conflicts
0xcb45d9d6…cb87
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0012
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001f
0x1b6862…e19c
4 touches
1 conflict
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
21 conflicts on slot 0xed571fa68f…a66a38
Audit this contract →
← previous block·next block →recent activity