← previous blocknext block →recent activity
Analyzing
Block #80,230,666
19 transactions · 12 stateful · 2026-06-09 21:46:28 UTC
Parallelism
84/100
Blocked
17%
Avg conflicts / tx
0.11
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #80,230,666 · 19 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
1w02w13w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x86e6cece…1fd5
0x2a68ba…90c5
2 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x1638f24a…aa67
0x065c9d…c394
2 touches
0 conflicts
0x34386044…cd63
0x065c9d…c394
2 touches
0 conflicts
0x44cd4df5…59c6
0x065c9d…c394
2 touches
0 conflicts
0x48f2092d…f818
0x065c9d…c394
2 touches
0 conflicts
0x89374dbf…35fe
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 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity