← previous blocknext block →recent activity
Analyzing
Block #77,184,687
15 transactions · 12 stateful · 2026-05-26 18:58:25 UTC
Parallelism
73/100
Blocked
33%
Avg conflicts / tx
0.33
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #77,184,687 · 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
1w04w06w17w28w111w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xc51d3663…0f45
0xa6afd3…d132
4 touches
1 conflict
0xd71a331e…42ea
0xa6afd3…d132
4 touches
1 conflict
0x8ed1f2d3…6b38
0x065c9d…c394
2 touches
0 conflicts
0x95523e2a…4c01
0x065c9d…c394
2 touches
0 conflicts
0xa1a3ba60…77c9
0x065c9d…c394
2 touches
0 conflicts
0xe9a18eff…4d64
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: Kuru Exchange: Market-WETH/USDC
3 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity