← previous blocknext block →recent activity
Analyzing
Block #77,350,628
16 transactions · 12 stateful · 2026-05-27 13:27:12 UTC
Parallelism
88/100
Blocked
17%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #77,350,628 · 16 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w111w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x54c67d3e…a19f
0x065c9d…c394
4 touches
1 conflict
0x0d622e34…0000
0x681e90…ae09
4 touches
1 conflict
0x757f67f2…9b3a
0x065c9d…c394
3 touches
1 conflict
0xb4f03087…0886
0x065c9d…c394
3 touches
1 conflict
0x0823c566…b485
0x065c9d…c394
2 touches
0 conflicts
0x0941dc41…5b53
0x065c9d…c394
2 touches
0 conflicts
0x10e9f199…41bf
0x065c9d…c394
2 touches
0 conflicts
0x18cf3003…51d1
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
1 conflict on slot 0x54c67d3ebc…47a19f
Audit this contract →
← previous block·next block →recent activity