← previous blocknext block →recent activity
Analyzing
Block #80,408,089
17 transactions · 10 stateful · 2026-06-10 17:29:11 UTC
Parallelism
82/100
Blocked
20%
Avg conflicts / tx
0.18
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #80,408,089 · 17 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
1w02w14w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5540f956…69e8
0x065c9d…c394
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x20f3041f…1688
0x065c9d…c394
2 touches
0 conflicts
0x45550d84…bc01
0x065c9d…c394
2 touches
0 conflicts
0x89b83e87…359f
0x065c9d…c394
2 touches
0 conflicts
0x915a3b9f…6d69
0x065c9d…c394
2 touches
0 conflicts
0xb27e53cd…7768
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 0x5540f95607…2d69e8
Audit this contract →
← previous block·next block →recent activity