← previous blocknext block →recent activity
Analyzing
Block #80,822,799
15 transactions · 12 stateful · 2026-06-12 15:34:59 UTC
Parallelism
73/100
Blocked
25%
Avg conflicts / tx
0.4
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #80,822,799 · 15 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
1w02w16w27w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0x21898044…a071
0x065c9d…c394
4 touches
1 conflict
0x28a7ca1f…30c3
0x065c9d…c394
2 touches
0 conflicts
0x518506cf…9fa2
0x065c9d…c394
2 touches
0 conflicts
0x5583dfcd…6c64
0x065c9d…c394
2 touches
0 conflicts
0x7af0bd79…fca9
0x065c9d…c394
2 touches
0 conflicts
0xae90214c…4fb3
0x065c9d…c394
2 touches
0 conflicts
0xc4cf2032…bc6a
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
6 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity