← previous blocknext block →recent activity
Analyzing
Block #77,239,023
8 transactions · 6 stateful · 2026-05-27 01:03:22 UTC
Parallelism
75/100
Blocked
17%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #77,239,023 · 8 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
1w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcabd59d2…bebd
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x36a50b5e…0482
0x065c9d…c394
3 touches
1 conflict
0xdc92db90…3d7c
0x065c9d…c394
3 touches
1 conflict
0x95523e2a…4c01
0x065c9d…c394
2 touches
0 conflicts
0xb2399477…70da
0x065c9d…c394
2 touches
0 conflicts
0xc9a8c7e1…d460
0x065c9d…c394
2 touches
0 conflicts
0x06e40499…165e
0x1d1325…2305
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 0xcabd59d295…2abebd
Audit this contract →
← previous block·next block →recent activity