← previous blocknext block →recent activity
Analyzing
Block #73,744,030
32 transactions · 21 stateful · 2026-05-10 20:25:37 UTC
Parallelism
69/100
Blocked
71%
Avg conflicts / tx
1.72
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #73,744,030 · 32 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
1w02w13w24w35w46w57w68w713w814w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x26d4b0d7…be8c
0xd32edf…ff58
19 touches
45 conflicts
0x0ac31945…2c72
0x065c9d…c394
6 touches
3 conflicts
0x529acb6a…fcc6
0x065c9d…c394
6 touches
3 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x00000000…001d
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002d
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
45 conflicts on slot 0x26d4b0d70f…b6be8c
Audit this contract →
← previous block·next block →recent activity