← previous blocknext block →recent activity
Analyzing
Block #80,231,043
17 transactions · 14 stateful · 2026-06-09 21:49:00 UTC
Parallelism
82/100
Blocked
14%
Avg conflicts / tx
0.24
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #80,231,043 · 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
2w03w14w05w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x820b1c27…3b18
0x065c9d…c394
4 touches
1 conflict
0x21898044…a071
0x065c9d…c394
4 touches
1 conflict
0x046a928e…0012
0x2a68ba…90c5
4 touches
1 conflict
0x957a33c2…b592
0x065c9d…c394
2 touches
0 conflicts
0xf317a940…6511
0x065c9d…c394
2 touches
0 conflicts
0x44ad89ba…cf83
0x23c26b…7777
2 touches
0 conflicts
0x81a7ba4d…8c4b
0x23c26b…7777
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 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity