← previous blocknext block →recent activity
Analyzing
Block #80,276,932
16 transactions · 14 stateful · 2026-06-10 02:55:04 UTC
Parallelism
81/100
Blocked
21%
Avg conflicts / tx
0.25
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #80,276,932 · 16 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
2w03w14w15w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0xdf222f84…4125
0x065c9d…c394
3 touches
1 conflict
0x063ce682…9990
0x065c9d…c394
3 touches
1 conflict
0x48977435…3d56
0x065c9d…c394
2 touches
0 conflicts
0x972ce83a…194a
0x065c9d…c394
2 touches
0 conflicts
0xad810d62…3eb5
0x065c9d…c394
2 touches
0 conflicts
0x00000000…0012
0x1b6862…e19c
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