← previous blocknext block →recent activity
Analyzing
Block #80,754,303
15 transactions · 14 stateful · 2026-06-12 07:58:15 UTC
Parallelism
80/100
Blocked
14%
Avg conflicts / tx
0.2
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #80,754,303 · 15 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
1w04w15w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x21898044…a071
0x065c9d…c394
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x3234df7e…62ef
0x065c9d…c394
2 touches
0 conflicts
0x53b7c26f…afdb
0x065c9d…c394
2 touches
0 conflicts
0x8ea8eec1…a40b
0x065c9d…c394
2 touches
0 conflicts
0xa6ccc83e…4e30
0x065c9d…c394
2 touches
0 conflicts
0xd2d278e9…34e7
0x065c9d…c394
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