← previous blocknext block →recent activity
Analyzing
Block #77,238,682
11 transactions · 11 stateful · 2026-05-27 01:01:06 UTC
Parallelism
82/100
Blocked
9%
Avg conflicts / tx
0.18
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #77,238,682 · 11 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
1w04w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x95523e2a…4c01
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x30c81696…e76b
0x065c9d…c394
4 touches
1 conflict
0x77ed432f…fa04
0x065c9d…c394
4 touches
1 conflict
0x16fb9794…0d2e
0x065c9d…c394
3 touches
1 conflict
0x827e8d7d…fa4a
0x065c9d…c394
3 touches
1 conflict
0x4aa4f53b…89a0
0x188d58…ea8e
2 touches
0 conflicts
0x6f75cf07…fdbd
0x188d58…ea8e
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 0x95523e2aaf…734c01
Audit this contract →
← previous block·next block →recent activity