← previous blocknext block →recent activity
Analyzing
Block #80,309,559
21 transactions · 12 stateful · 2026-06-10 06:32:33 UTC
Parallelism
86/100
Blocked
25%
Avg conflicts / tx
0.19
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #80,309,559 · 21 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
1w02w03w04w16w28w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9a4658fd…c4d5
0x065c9d…c394
4 touches
1 conflict
0x046a928e…0012
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x97140354…16f8
0x065c9d…c394
3 touches
1 conflict
0x1a082399…5cfe
0x065c9d…c394
2 touches
0 conflicts
0x3344e9fa…65d9
0x065c9d…c394
2 touches
0 conflicts
0x5807062b…ea49
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 0x9a4658fda1…efc4d5
Audit this contract →
← previous block·next block →recent activity