← previous blocknext block →recent activity
Analyzing
Block #80,077,083
14 transactions · 12 stateful · 2026-06-09 04:42:58 UTC
Parallelism
79/100
Blocked
25%
Avg conflicts / tx
0.29
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #80,077,083 · 14 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
1w02w03w14w212w013w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5540f956…69e8
0x065c9d…c394
4 touches
1 conflict
0x53b4ef2b…8a05
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x04356a4d…b84b
0x065c9d…c394
2 touches
0 conflicts
0x1243f6ba…6fbf
0x065c9d…c394
2 touches
0 conflicts
0x15356c84…0e36
0x065c9d…c394
2 touches
0 conflicts
0x8a2be43d…8c49
0x065c9d…c394
2 touches
0 conflicts
0xab51a899…4d03
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 0x5540f95607…2d69e8
Audit this contract →
← previous block·next block →recent activity