← previous blocknext block →recent activity
Analyzing
Block #77,349,264
11 transactions · 9 stateful · 2026-05-27 13:18:09 UTC
Parallelism
73/100
Blocked
33%
Avg conflicts / tx
0.36
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #77,349,264 · 11 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
1w05w16w17w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x63591fa8…d568
0x065c9d…c394
4 touches
1 conflict
0x8ec129f3…7953
0x065c9d…c394
3 touches
1 conflict
0xf0c1bc47…5a01
0x065c9d…c394
3 touches
1 conflict
0x6e204b4f…4b06
0x065c9d…c394
3 touches
1 conflict
0x85f9caef…2119
0x065c9d…c394
3 touches
1 conflict
0xe94167b8…3d04
0x1efe02…37d6
2 touches
0 conflicts
0xf298c368…a481
0x1efe02…37d6
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