← previous blocknext block →recent activity
Analyzing
Block #80,743,470
18 transactions · 15 stateful · 2026-06-12 06:46:02 UTC
Parallelism
83/100
Blocked
20%
Avg conflicts / tx
0.22
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #80,743,470 · 18 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
1w03w04w17w215w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa256c56e…1e46
0x065c9d…c394
4 touches
1 conflict
0x0d622e34…0000
0x681e90…ae09
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xe0316344…c8b2
0x065c9d…c394
3 touches
1 conflict
0x268f33bb…7cfd
0x065c9d…c394
3 touches
1 conflict
0x643145d3…efa4
0x065c9d…c394
2 touches
0 conflicts
0x7bc3a9df…e937
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 0xa256c56e3a…fc1e46
Audit this contract →
← previous block·next block →recent activity