← previous blocknext block →recent activity
Analyzing
Block #77,182,939
13 transactions · 11 stateful · 2026-05-26 18:46:45 UTC
Parallelism
77/100
Blocked
18%
Avg conflicts / tx
0.31
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #77,182,939 · 13 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
1w05w06w17w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0x99a21305…dffc
0x2a68ba…90c5
4 touches
1 conflict
0x68ced7c5…7e0a
0xa6afd3…d132
4 touches
1 conflict
0xc51d3663…0f45
0xa6afd3…d132
4 touches
1 conflict
0xd71a331e…42ea
0xa6afd3…d132
4 touches
1 conflict
0x2142712a…f881
0x065c9d…c394
2 touches
0 conflicts
0x47ef496e…17e7
0x065c9d…c394
2 touches
0 conflicts
0x24781048…4772
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
3 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity