← previous blocknext block →recent activity
Analyzing
Block #76,090,561
19 transactions · 13 stateful · 2026-05-21 17:33:30 UTC
Parallelism
63/100
Blocked
54%
Avg conflicts / tx
1
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #76,090,561 · 19 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
1w02w13w24w35w46w510w611w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6c628c08…4086
0xd32edf…ff58
11 touches
15 conflicts
0xb6d6d740…e91e
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0013
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0x046a928e…0012
0x2a68ba…90c5
6 touches
3 conflicts
0xdcdf5898…716b
0x065c9d…c394
5 touches
3 conflicts
0x00000000…002c
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
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 0x6c628c089b…c34086
Audit this contract →
← previous block·next block →recent activity