← previous blocknext block →recent activity
Analyzing
Block #80,653,535
18 transactions · 14 stateful · 2026-06-11 20:46:27 UTC
Parallelism
78/100
Blocked
29%
Avg conflicts / tx
0.33
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #80,653,535 · 18 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
1w02w03w14w25w37w08w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x00000000…0002
0x6fae99…a56d
4 touches
1 conflict
0xa60775f6…2345
0x065c9d…c394
3 touches
1 conflict
0x9d3f2124…725b
0x2a68ba…90c5
3 touches
1 conflict
0x7779ad8c…5669
0x065c9d…c394
3 touches
1 conflict
0xb182933f…46ed
0x754704…b603
2 touches
1 conflict
0x202187a3…9f8d
0x40c49f…2af0
2 touches
0 conflicts
0x25ecea76…bc30
0x40c49f…2af0
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