← previous blocknext block →recent activity
Analyzing
Block #80,102,038
22 transactions · 17 stateful · 2026-06-09 07:29:14 UTC
Parallelism
77/100
Blocked
53%
Avg conflicts / tx
0.64
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #80,102,038 · 22 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w14w25w26w37w48w09w112w014w216w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9ff176a9…152e
0x065c9d…c394
6 touches
3 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x33b74bf3…d88c
0xa6afd3…d132
4 touches
1 conflict
0xfe1362cf…bb85
0xa6afd3…d132
4 touches
1 conflict
0x8b305a3b…1c35
0x34b655…2a6f
4 touches
1 conflict
0x90f07a4f…d932
0x34b655…2a6f
4 touches
1 conflict
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 0x9ff176a9ad…67152e
Audit this contract →
← previous block·next block →recent activity