← previous blocknext block →recent activity
Analyzing
Block #80,679,964
16 transactions · 16 stateful · 2026-06-11 23:42:33 UTC
Parallelism
81/100
Blocked
19%
Avg conflicts / tx
0.31
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #80,679,964 · 16 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
1w03w04w15w213w014w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x719b3398…442c
0x065c9d…c394
4 touches
1 conflict
0x160f117d…8e90
0x065c9d…c394
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x8f79b556…30e4
0x065c9d…c394
3 touches
1 conflict
0x2f1227af…b196
0x065c9d…c394
3 touches
1 conflict
0xe5d8eb1c…e7d9
0x065c9d…c394
3 touches
1 conflict
0xeec7f1c4…a1a0
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
3 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity