← previous blocknext block →recent activity
Analyzing
Block #76,089,044
23 transactions · 16 stateful · 2026-05-21 17:23:24 UTC
Parallelism
70/100
Blocked
69%
Avg conflicts / tx
1.17
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #76,089,044 · 23 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w68w011w112w518w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe2ea1ca4…2f8e
0xd32edf…ff58
13 touches
21 conflicts
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x91945265…e58f
0x1b6862…e19c
4 touches
1 conflict
0x0aa885fa…a3d1
0x2a68ba…90c5
4 touches
1 conflict
0x99a21305…dffc
0x2a68ba…90c5
4 touches
1 conflict
0x60f7fbaf…bd58
0x34b655…2a6f
4 touches
1 conflict
0x99f080dc…58c1
0x34b655…2a6f
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
21 conflicts on slot 0xe2ea1ca472…3a2f8e
Audit this contract →
← previous block·next block →recent activity