← previous blocknext block →recent activity
Analyzing
Block #77,515,802
9 transactions · 7 stateful · 2026-05-28 07:47:31 UTC
Parallelism
67/100
Blocked
43%
Avg conflicts / tx
0.44
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #77,515,802 · 9 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
1w02w13w24w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xa12cdc55…6e55
0x065c9d…c394
4 touches
1 conflict
0x33a01221…323f
0x065c9d…c394
4 touches
1 conflict
0x49cbdb1b…bda4
0x065c9d…c394
4 touches
1 conflict
0x105d98e4…c5bc
0x065c9d…c394
4 touches
1 conflict
0x17361987…ed32
0x065c9d…c394
3 touches
1 conflict
0xab977653…6323
0x065c9d…c394
3 touches
1 conflict
0x04f4b4b0…4479
0x065c9d…c394
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