← previous blocknext block →recent activity
Analyzing
Block #77,184,792
15 transactions · 13 stateful · 2026-05-26 18:59:07 UTC
Parallelism
67/100
Blocked
38%
Avg conflicts / tx
0.73
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #77,184,792 · 15 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
1w02w13w04w15w26w37w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0xa6afd3…d132
10 touches
10 conflicts
0xc51d3663…0f45
0xa6afd3…d132
6 touches
3 conflicts
0xd71a331e…42ea
0xa6afd3…d132
6 touches
3 conflicts
0x7e9d9902…1e17
0xa6afd3…d132
3 touches
1 conflict
0xe489268d…947b
0x405b63…7777
2 touches
1 conflict
0x24781048…4772
0x2a68ba…90c5
2 touches
0 conflicts
0x99a21305…dffc
0x2a68ba…90c5
2 touches
0 conflicts
0xe2e94dfa…5026
0x2a68ba…90c5
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
10 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity