← previous blocknext block →recent activity
Analyzing
Block #80,217,242
19 transactions · 14 stateful · 2026-06-09 20:17:06 UTC
Parallelism
74/100
Blocked
36%
Avg conflicts / tx
0.37
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #80,217,242 · 19 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w15w27w38w49w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x160f117d…8e90
0x065c9d…c394
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0xb33ff823…1188
0x065c9d…c394
4 touches
1 conflict
0xfe9f1ee0…185c
0xd32edf…ff58
3 touches
1 conflict
0x3c183e47…33e1
0x065c9d…c394
3 touches
1 conflict
0xfa84f26a…d000
0x065c9d…c394
3 touches
1 conflict
0x373f6b9a…85c3
0x065c9d…c394
3 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: Market-MON/USDC
3 conflicts on slot 0x160f117d43…518e90
Audit this contract →
← previous block·next block →recent activity