← previous blocknext block →recent activity
Analyzing
Block #77,237,959
10 transactions · 9 stateful · 2026-05-27 00:56:18 UTC
Parallelism
70/100
Blocked
33%
Avg conflicts / tx
0.5
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #77,237,959 · 10 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
1w02w03w04w17w28w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0x77ed432f…fa04
0x065c9d…c394
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0xe8aab7db…a319
0xa6afd3…d132
4 touches
1 conflict
0x0dcf62c8…556c
0x065c9d…c394
2 touches
0 conflicts
0x12cdaf06…570d
0x065c9d…c394
2 touches
0 conflicts
0x2bd61bb6…1df0
0x065c9d…c394
2 touches
0 conflicts
0x3bc9723e…4dcf
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