← previous blocknext block →recent activity
Analyzing
Block #77,553,771
15 transactions · 12 stateful · 2026-05-28 12:00:24 UTC
Parallelism
73/100
Blocked
42%
Avg conflicts / tx
0.4
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #77,553,771 · 15 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w39w010w111w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc358c73e…b289
0xd32edf…ff58
5 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xce827910…ff22
0x065c9d…c394
4 touches
1 conflict
0xf9b8ae99…32b3
0x34b655…2a6f
4 touches
1 conflict
0xf9b8ae99…32b4
0x34b655…2a6f
4 touches
1 conflict
0x39a89a77…686c
0x065c9d…c394
2 touches
0 conflicts
0x3b3c0d43…58ff
0x065c9d…c394
2 touches
0 conflicts
0xfc15bcec…d8f7
0x065c9d…c394
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
3 conflicts on slot 0xc358c73e03…6fb289
Audit this contract →
← previous block·next block →recent activity