← previous blocknext block →recent activity
Analyzing
Block #77,236,389
14 transactions · 11 stateful · 2026-05-27 00:45:50 UTC
Parallelism
79/100
Blocked
27%
Avg conflicts / tx
0.36
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #77,236,389 · 14 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
1w02w04w15w210w011w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x77ed432f…fa04
0x065c9d…c394
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x00032a6d…38b4
0x065c9d…c394
2 touches
0 conflicts
0x1e4ca41e…377e
0x065c9d…c394
2 touches
0 conflicts
0x9421f3dc…55a5
0x065c9d…c394
2 touches
0 conflicts
0xa7313e3d…abe6
0x065c9d…c394
2 touches
0 conflicts
0xb3a2ea1b…e8d0
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-MON/USDC
3 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity