← previous blocknext block →recent activity
Analyzing
Block #76,034,036
20 transactions · 17 stateful · 2026-05-21 11:16:25 UTC
Parallelism
60/100
Blocked
41%
Avg conflicts / tx
0.95
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #76,034,036 · 20 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
1w02w13w24w35w46w57w69w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc1fdfb2f…01ff
0xd32edf…ff58
11 touches
15 conflicts
0x046a928e…0012
0x2a68ba…90c5
6 touches
3 conflicts
0x14d1bf0e…e09c
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0013
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…002b
0x1b6862…e19c
4 touches
1 conflict
0x443a3e47…f4a4
0x065c9d…c394
4 touches
1 conflict
0x4defe5ba…5900
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
15 conflicts on slot 0xc1fdfb2f11…6f01ff
Audit this contract →
← previous block·next block →recent activity