← previous blocknext block →recent activity
Analyzing
Block #73,578,146
19 transactions · 16 stateful · 2026-05-10 01:50:38 UTC
Parallelism
58/100
Blocked
56%
Avg conflicts / tx
1.58
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #73,578,146 · 19 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
1w02w13w24w35w46w57w612w713w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf3b79944…ebf2
0xd32edf…ff58
15 touches
28 conflicts
0x506eaf48…7670
0x065c9d…c394
4 touches
1 conflict
0xba5743c7…21c1
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001a
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002a
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0xc9e97522…3519
0x2a68ba…90c5
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
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
28 conflicts on slot 0xf3b79944e6…f6ebf2
Audit this contract →
← previous block·next block →recent activity