← previous blocknext block →recent activity
Analyzing
Block #75,864,114
25 transactions · 19 stateful · 2026-05-20 16:25:15 UTC
Parallelism
76/100
Blocked
47%
Avg conflicts / tx
0.76
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #75,864,114 · 25 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w27w38w09w112w414w016w117w218w023w124w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0ef63c59…7b4d
0xd32edf…ff58
11 touches
15 conflicts
0x60f7fbaf…bd58
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0xba5743c7…21bf
0x1b6862…e19c
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x0d622e34…0000
0x681e90…ae09
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x00000000…0015
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
15 conflicts on slot 0x0ef63c5903…697b4d
Audit this contract →
← previous block·next block →recent activity