← previous blocknext block →recent activity
Analyzing
Block #80,278,279
23 transactions · 20 stateful · 2026-06-10 03:04:03 UTC
Parallelism
83/100
Blocked
45%
Avg conflicts / tx
0.52
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #80,278,279 · 23 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w25w26w310w011w115w118w020w121w122w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xb4e0a934…5fc7
0x34b655…2a6f
6 touches
3 conflicts
0x80afd9d9…57cf
0x065c9d…c394
6 touches
3 conflicts
0x7b9a42f7…7b88
0xa6afd3…d132
4 touches
1 conflict
0x21898044…a071
0x065c9d…c394
4 touches
1 conflict
0x61589664…4bd6
0x34b655…2a6f
4 touches
1 conflict
0x6f6b4878…d72d
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 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity