← previous blocknext block →recent activity
Analyzing
Block #77,784,936
11 transactions · 11 stateful · 2026-05-29 13:42:13 UTC
Parallelism
73/100
Blocked
36%
Avg conflicts / tx
0.45
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #77,784,936 · 11 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
1w03w14w05w16w29w2
- 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
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x55ed4390…77d4
0xa6afd3…d132
4 touches
1 conflict
0x94c21920…5885
0xa6afd3…d132
4 touches
1 conflict
0x7640ebbc…c387
0x065c9d…c394
2 touches
0 conflicts
0xd76f53a2…09fd
0x065c9d…c394
2 touches
0 conflicts
0xfc0b8af8…25e5
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