← previous blocknext block →recent activity
Analyzing
Block #80,251,593
10 transactions · 7 stateful · 2026-06-10 00:06:08 UTC
Parallelism
70/100
Blocked
29%
Avg conflicts / tx
0.4
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #80,251,593 · 10 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
1w02w03w14w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x079e4da6…0c44
0x065c9d…c394
2 touches
0 conflicts
0x43f48b58…0c6e
0x065c9d…c394
2 touches
0 conflicts
0x7bbaef50…5f39
0x065c9d…c394
2 touches
0 conflicts
0xac4ff825…e46e
0x065c9d…c394
2 touches
0 conflicts
0xe2f62e71…2a84
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: MarginAccount
3 conflicts on slot 0xf2f76ab392…f3623e
Audit this contract →
← previous block·next block →recent activity