← previous blocknext block →recent activity
Analyzing
Block #77,237,678
17 transactions · 13 stateful · 2026-05-27 00:54:25 UTC
Parallelism
88/100
Blocked
23%
Avg conflicts / tx
0.18
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #77,237,678 · 17 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
1w02w03w14w110w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x77ed432f…fa04
0x065c9d…c394
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x3a26749a…c51a
0xd32edf…ff58
3 touches
1 conflict
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x03cd7928…1391
0x065c9d…c394
2 touches
0 conflicts
0x12cdaf06…570d
0x065c9d…c394
2 touches
0 conflicts
0x2b38ad92…cf8a
0x065c9d…c394
2 touches
0 conflicts
0x77349b69…f0c9
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
1 conflict on slot 0x77ed432f03…d6fa04
Audit this contract →
← previous block·next block →recent activity