← previous blocknext block →recent activity
Analyzing
Block #76,039,657
23 transactions · 19 stateful · 2026-05-21 11:53:50 UTC
Parallelism
70/100
Blocked
47%
Avg conflicts / tx
1.13
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #76,039,657 · 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
4w07w08w19w010w112w013w114w215w316w417w519w622w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x065e538a…8830
0xd32edf…ff58
13 touches
21 conflicts
0x443a3e47…f4a4
0x065c9d…c394
6 touches
3 conflicts
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002b
0x1b6862…e19c
4 touches
1 conflict
0xd381d0e5…7434
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x145554b9…8b5f
0x34b655…2a6f
4 touches
1 conflict
0x676f9f01…a8ac
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 0x065e538a4c…d48830
Audit this contract →
← previous block·next block →recent activity