← previous blocknext block →recent activity
Analyzing
Block #77,433,581
12 transactions · 9 stateful · 2026-05-27 22:39:48 UTC
Parallelism
83/100
Blocked
11%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #77,433,581 · 12 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
2w03w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x28666bfa…f72e
0x065c9d…c394
3 touches
1 conflict
0x2e663ad9…4420
0x065c9d…c394
3 touches
1 conflict
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x231189ba…1f6b
0x065c9d…c394
2 touches
0 conflicts
0x32bbc2f1…cb4a
0x065c9d…c394
2 touches
0 conflicts
0x52e69143…95ad
0x065c9d…c394
2 touches
0 conflicts
0x5ab4be4e…1ce5
0x065c9d…c394
2 touches
0 conflicts
0xb0fec4a8…0a54
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 0x28666bfac8…54f72e
Audit this contract →
← previous block·next block →recent activity