← previous blocknext block →recent activity
Analyzing
Block #77,340,586
18 transactions · 9 stateful · 2026-05-27 12:20:24 UTC
Parallelism
89/100
Blocked
11%
Avg conflicts / tx
0.06
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #77,340,586 · 18 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
2w015w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca7b0333…a71c
0x065c9d…c394
4 touches
1 conflict
0xf2325d1e…cdfe
0x065c9d…c394
4 touches
1 conflict
0x77ed432f…fa04
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x971ffd0b…3ad6
0x065c9d…c394
4 touches
1 conflict
0x41ea893f…1c6c
0x065c9d…c394
3 touches
1 conflict
0x88f35b26…267a
0x065c9d…c394
3 touches
1 conflict
0x36c2e09d…c5b1
0x065c9d…c394
3 touches
1 conflict
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 0xca7b03331b…54a71c
Audit this contract →
← previous block·next block →recent activity