← previous blocknext block →recent activity
Analyzing
Block #80,265,608
12 transactions · 10 stateful · 2026-06-10 01:39:35 UTC
Parallelism
83/100
Blocked
10%
Avg conflicts / tx
0.17
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #80,265,608 · 12 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
1w02w03w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x21898044…a071
0x065c9d…c394
4 touches
1 conflict
0xf635a831…11e6
0x065c9d…c394
3 touches
1 conflict
0xd3aea89f…ff8e
0x065c9d…c394
3 touches
1 conflict
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x11e1fef0…f6ba
0x065c9d…c394
2 touches
0 conflicts
0x2f4c8523…f788
0x065c9d…c394
2 touches
0 conflicts
0xe5a4054f…3a16
0x065c9d…c394
2 touches
0 conflicts
0x046a928e…0012
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 0x2189804463…a2a071
Audit this contract →
← previous block·next block →recent activity