← previous blocknext block →recent activity
Analyzing
Block #71,044,914
20 transactions · 17 stateful · 2026-04-28 08:31:50 UTC
Parallelism
75/100
Blocked
47%
Avg conflicts / tx
0.65
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #71,044,914 · 20 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w15w07w28w09w111w112w213w314w419w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x634a5183…5f1f
0xd32edf…ff58
7 touches
6 conflicts
0x581c8b84…9fe8
0xa6afd3…d132
6 touches
3 conflicts
0x11b69a7e…334e
0xee8c0e…1242
6 touches
3 conflicts
0x92d610a6…9a40
0x2a68ba…90c5
6 touches
3 conflicts
0xa4e3b3b1…0911
0x2a68ba…90c5
6 touches
3 conflicts
0x1ab65a45…75bb
0x065c9d…c394
6 touches
3 conflicts
0xcd510377…571e
0xee8c0e…1242
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
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
6 conflicts on slot 0x634a518394…4e5f1f
Audit this contract →
← previous block·next block →recent activity