← previous blocknext block →recent activity
Analyzing
Block #77,783,665
26 transactions · 18 stateful · 2026-05-29 13:33:46 UTC
Parallelism
73/100
Blocked
50%
Avg conflicts / tx
0.65
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #77,783,665 · 26 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
1w02w13w25w06w37w48w516w017w119w623w024w125w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x52e69143…95ad
0x065c9d…c394
6 touches
3 conflicts
0x40e31e14…c46c
0xa6afd3…d132
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0x6b43b3f1…84b0
0xd32edf…ff58
5 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001e
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: Kuru Exchange: Market-MON/USDC
6 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity