← previous blocknext block →recent activity
Analyzing
Block #77,182,623
25 transactions · 18 stateful · 2026-05-26 18:44:39 UTC
Parallelism
88/100
Blocked
28%
Avg conflicts / tx
0.28
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #77,182,623 · 25 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w07w08w19w112w213w116w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0xdfbf3c59…e164
0xd32edf…ff58
5 touches
3 conflicts
0x046a928e…0012
0x2a68ba…90c5
4 touches
1 conflict
0xc51d3663…0f45
0xa6afd3…d132
4 touches
1 conflict
0x18aed20c…48f3
0x000000…012a
2 touches
0 conflicts
0x7b43f938…3650
0x000000…012a
2 touches
0 conflicts
0x5a646640…4deb
0x065c9d…c394
2 touches
0 conflicts
0x01e7b865…6e6d
0x188d58…ea8e
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: Kuru Exchange: Market-WETH/USDC
3 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity