← previous blocknext block →recent activity
Analyzing
Block #76,527,263
17 transactions · 13 stateful · 2026-05-23 18:01:26 UTC
Parallelism
71/100
Blocked
46%
Avg conflicts / tx
0.76
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #76,527,263 · 17 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
1w02w13w26w37w09w310w112w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x673a3b1a…ed5c
0xd32edf…ff58
9 touches
10 conflicts
0xd59f6ed1…03e9
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001d
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002d
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
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
10 conflicts on slot 0x673a3b1ab8…23ed5c
Audit this contract →
← previous block·next block →recent activity