← previous blocknext block →recent activity
Analyzing
Block #77,240,477
13 transactions · 11 stateful · 2026-05-27 01:13:08 UTC
Parallelism
77/100
Blocked
27%
Avg conflicts / tx
0.31
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #77,240,477 · 13 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
1w02w03w16w17w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x95523e2a…4c01
0x065c9d…c394
4 touches
1 conflict
0x77ed432f…fa04
0x065c9d…c394
4 touches
1 conflict
0x6b228292…9272
0x065c9d…c394
2 touches
0 conflicts
0x7e87fd96…f01f
0x065c9d…c394
2 touches
0 conflicts
0x88198c12…a5d6
0x065c9d…c394
2 touches
0 conflicts
0xa4cc43e1…56e1
0x065c9d…c394
2 touches
0 conflicts
0xba2d3c7e…d8bc
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