← previous blocknext block →recent activity
Analyzing
Block #80,076,754
33 transactions · 23 stateful · 2026-06-09 04:40:45 UTC
Parallelism
88/100
Blocked
43%
Avg conflicts / tx
0.39
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #80,076,754 · 33 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w26w27w011w012w115w016w118w019w120w221w129w331w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2bebafe3…85fe
0x065c9d…c394
6 touches
3 conflicts
0xc3c8642a…7da5
0x2a68ba…90c5
6 touches
3 conflicts
0x90f07a4f…d932
0x34b655…2a6f
6 touches
3 conflicts
0xa1087a5c…66c4
0x754704…b603
6 touches
3 conflicts
0x22e0cc1d…ad04
0x34b655…2a6f
4 touches
1 conflict
0x30aa9d2b…607a
0xdd0a93…ece5
4 touches
1 conflict
0xf35cbc81…32e4
0xdd0a93…ece5
4 touches
1 conflict
0x13a54fa2…5ae3
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: Market-MON/USDC
3 conflicts on slot 0x2bebafe3d5…aa85fe
Audit this contract →
← previous block·next block →recent activity