← previous blocknext block →recent activity
Analyzing
Block #77,354,961
12 transactions · 8 stateful · 2026-05-27 13:56:03 UTC
Parallelism
83/100
Blocked
13%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #77,354,961 · 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
1w02w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcc8faac2…c766
0x065c9d…c394
4 touches
1 conflict
0x4c1f11de…1de1
0x065c9d…c394
3 touches
1 conflict
0x0cd30e33…e2b8
0x065c9d…c394
3 touches
1 conflict
0x1169283c…1b73
0x065c9d…c394
2 touches
0 conflicts
0x7f50612c…11fd
0x065c9d…c394
2 touches
0 conflicts
0xd3f6806d…7c88
0x065c9d…c394
2 touches
0 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
2 touches
0 conflicts
0x2f88a23f…9dc5
0x2a68ba…90c5
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 0xcc8faac238…88c766
Audit this contract →
← previous block·next block →recent activity