← previous blocknext block →recent activity
Analyzing
Block #80,224,104
14 transactions · 12 stateful · 2026-06-09 21:02:45 UTC
Parallelism
86/100
Blocked
25%
Avg conflicts / tx
0.21
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #80,224,104 · 14 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
1w02w13w112w013w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6323f496…b0ca
0x065c9d…c394
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x92339d95…0800
0x0000a8…8888
4 touches
1 conflict
0x50a49698…2bbb
0xd32edf…ff58
3 touches
1 conflict
0x01e7b865…6e6e
0x188d58…ea8e
2 touches
0 conflicts
0xe75ce681…ba5f
0x188d58…ea8e
2 touches
0 conflicts
0xe75ce681…ba61
0x188d58…ea8e
2 touches
0 conflicts
0x00000000…0012
0x1b6862…e19c
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 0x6323f49649…70b0ca
Audit this contract →
← previous block·next block →recent activity