← previous blocknext block →recent activity
Analyzing
Block #80,825,776
20 transactions · 12 stateful · 2026-06-12 15:54:48 UTC
Parallelism
90/100
Blocked
8%
Avg conflicts / tx
0.1
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #80,825,776 · 20 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
1w03w04w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x66a1faa8…66ed
0x065c9d…c394
4 touches
1 conflict
0x86d4b68b…d2d6
0x065c9d…c394
4 touches
1 conflict
0x046a928e…0012
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x3b9bb58c…e73a
0x34b655…2a6f
2 touches
0 conflicts
0x482471ad…122f
0x34b655…2a6f
2 touches
0 conflicts
0x49611dcc…9864
0x34b655…2a6f
2 touches
0 conflicts
0x5fad6fee…7714
0x34b655…2a6f
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 0x66a1faa8e0…7266ed
Audit this contract →
← previous block·next block →recent activity