← previous blocknext block →recent activity
Analyzing
Block #76,241,871
14 transactions · 12 stateful · 2026-05-22 10:21:24 UTC
Parallelism
64/100
Blocked
42%
Avg conflicts / tx
0.79
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #76,241,871 · 14 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
1w02w13w24w38w19w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5358eb52…4bd2
0xd32edf…ff58
9 touches
10 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x3a49d735…87be
0x065c9d…c394
2 touches
0 conflicts
0x00000000…0012
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…0013
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…0015
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…001f
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…002f
0x1b6862…e19c
2 touches
0 conflicts
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 0x5358eb52d0…334bd2
Audit this contract →
← previous block·next block →recent activity