← previous blocknext block →recent activity
Analyzing
Block #73,751,060
30 transactions · 20 stateful · 2026-05-10 21:13:05 UTC
Parallelism
67/100
Blocked
50%
Avg conflicts / tx
1.27
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #73,751,060 · 30 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
1w02w13w24w35w46w57w68w79w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd116035a…b873
0xd32edf…ff58
17 touches
36 conflicts
0x792299c4…16b6
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0013
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0xb77dec5d…798e
0x065c9d…c394
4 touches
1 conflict
0x00000000…0012
0x1b6862…e19c
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0x968bdacb…f461
0x2a68ba…90c5
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
36 conflicts on slot 0xd116035aae…5fb873
Audit this contract →
← previous block·next block →recent activity