← previous blocknext block →recent activity
Analyzing
Block #77,220,586
10 transactions · 10 stateful · 2026-05-26 22:59:35 UTC
Parallelism
50/100
Blocked
40%
Avg conflicts / tx
0.8
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #77,220,586 · 10 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
1w03w14w25w37w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0xa6afd3…d132
8 touches
6 conflicts
0xc51d3663…0f45
0xa6afd3…d132
4 touches
1 conflict
0xd71a331e…42ea
0xa6afd3…d132
4 touches
1 conflict
0xf75930e6…82cc
0xa6afd3…d132
4 touches
1 conflict
0x9cb739c1…2510
0xa6afd3…d132
3 touches
1 conflict
0xec70a16c…5195
0xa6afd3…d132
3 touches
1 conflict
0x00000000…001b
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…002b
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: Kuru Exchange: Market-WETH/USDC
6 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity