← previous blocknext block →recent activity
Analyzing
Block #80,292,214
13 transactions · 12 stateful · 2026-06-10 04:36:57 UTC
Parallelism
77/100
Blocked
17%
Avg conflicts / tx
0.15
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #80,292,214 · 13 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
1w03w14w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x7c7b3b6f…6fef
0x000000…8ba3
2 touches
0 conflicts
0x47e43836…3860
0x065c9d…c394
2 touches
0 conflicts
0x8973c838…6871
0x065c9d…c394
2 touches
0 conflicts
0xc01405d2…3899
0x065c9d…c394
2 touches
0 conflicts
0xd70b679a…db81
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
1 conflict on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity