← previous blocknext block →recent activity
Analyzing
Block #80,292,029
11 transactions · 10 stateful · 2026-06-10 04:35:43 UTC
Parallelism
73/100
Blocked
20%
Avg conflicts / tx
0.18
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #80,292,029 · 11 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
1w02w13w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x867310f9…f2f3
0x065c9d…c394
4 touches
1 conflict
0x05e8525d…56f3
0x065c9d…c394
3 touches
1 conflict
0x6ece4458…167c
0x065c9d…c394
3 touches
1 conflict
0x6d383d1f…a65e
0x2a68ba…90c5
2 touches
1 conflict
0x32519680…92cd
0x065c9d…c394
2 touches
0 conflicts
0x3c096c7a…7e0e
0x065c9d…c394
2 touches
0 conflicts
0x046a928e…0012
0x2a68ba…90c5
2 touches
0 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
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 0x867310f99f…9cf2f3
Audit this contract →
← previous block·next block →recent activity