← previous blocknext block →recent activity
Analyzing
Block #73,270,939
24 transactions · 19 stateful · 2026-05-08 15:47:13 UTC
Parallelism
67/100
Blocked
63%
Avg conflicts / tx
1.46
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #73,270,939 · 24 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
1w02w13w24w35w46w57w613w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7934c615…60c2
0xd32edf…ff58
15 touches
28 conflicts
0x0d622e34…0000
0x681e90…ae09
6 touches
3 conflicts
0x60f7fbaf…bd58
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001c
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002c
0x1b6862…e19c
4 touches
1 conflict
0x8d47c9a4…f11e
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
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
28 conflicts on slot 0x7934c61528…8960c2
Audit this contract →
← previous block·next block →recent activity