← previous blocknext block →recent activity
Analyzing
Block #80,230,999
18 transactions · 13 stateful · 2026-06-09 21:48:43 UTC
Parallelism
89/100
Blocked
8%
Avg conflicts / tx
0.06
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #80,230,999 · 18 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf03018ac…1771
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xa8eba479…030d
0x065c9d…c394
3 touches
1 conflict
0x21898044…a071
0x065c9d…c394
2 touches
0 conflicts
0x34386044…cd63
0x065c9d…c394
2 touches
0 conflicts
0x8169bc8d…021b
0x065c9d…c394
2 touches
0 conflicts
0x9f6871c3…34c2
0x065c9d…c394
2 touches
0 conflicts
0xf6e7540d…fa28
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 0xf03018acad…e01771
Audit this contract →
← previous block·next block →recent activity