← previous blocknext block →recent activity
Analyzing
Block #77,782,763
18 transactions · 15 stateful · 2026-05-29 13:27:49 UTC
Parallelism
83/100
Blocked
27%
Avg conflicts / tx
0.39
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #77,782,763 · 18 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
3w04w05w18w09w113w214w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x4b5b8aed…b67b
0xd32edf…ff58
5 touches
3 conflicts
0x55ed4390…77d4
0xa6afd3…d132
4 touches
1 conflict
0xce827910…ff22
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x94c21920…5885
0xa6afd3…d132
4 touches
1 conflict
0x46ebe819…8e3f
0xa6afd3…d132
3 touches
1 conflict
0xba198004…2af4
0xa6afd3…d132
3 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
3 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity