← previous blocknext block →recent activity
Analyzing
Block #80,573,064
28 transactions · 27 stateful · 2026-06-11 11:49:01 UTC
Parallelism
79/100
Blocked
33%
Avg conflicts / tx
0.71
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #80,573,064 · 28 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w06w17w08w29w010w011w312w413w414w115w516w521w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf2f76ab3…623e
0x2a68ba…90c5
10 touches
10 conflicts
0x00000000…003d
0x40c49f…2af0
6 touches
3 conflicts
0x565818b0…80a3
0xa6afd3…d132
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x160f117d…8e90
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x342fbbca…d443
0x40c49f…2af0
4 touches
1 conflict
0xb3572c95…9c4a
0x2a68ba…90c5
4 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: MarginAccount
10 conflicts on slot 0xf2f76ab392…f3623e
Audit this contract →
← previous block·next block →recent activity