← previous blocknext block →recent activity
Analyzing
Block #80,612,974
10 transactions · 9 stateful · 2026-06-11 16:15:44 UTC
Parallelism
80/100
Blocked
22%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #80,612,974 · 10 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
1w04w18w09w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb33ff823…1188
0x065c9d…c394
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x160f117d…8e90
0x065c9d…c394
2 touches
0 conflicts
0x161cf752…6ab9
0x065c9d…c394
2 touches
0 conflicts
0x8acc9229…cc31
0x065c9d…c394
2 touches
0 conflicts
0x994e8297…56b6
0x065c9d…c394
2 touches
0 conflicts
0xb6483659…726a
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
1 conflict on slot 0xb33ff82315…a81188
Audit this contract →
← previous block·next block →recent activity