← previous blocknext block →recent activity
Analyzing
Block #77,239,063
12 transactions · 9 stateful · 2026-05-27 01:03:38 UTC
Parallelism
67/100
Blocked
33%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #77,239,063 · 12 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
2w03w14w27w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0xa6afd3…d132
8 touches
6 conflicts
0xdf8c628d…34f2
0xa6afd3…d132
4 touches
1 conflict
0xe8aab7db…a319
0xa6afd3…d132
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x12cdaf06…570d
0x065c9d…c394
2 touches
0 conflicts
0x18db33bc…0b80
0x065c9d…c394
2 touches
0 conflicts
0x3013b4b9…d65f
0x065c9d…c394
2 touches
0 conflicts
0xc107c330…adf8
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
6 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity