← previous blocknext block →recent activity
Analyzing
Block #80,254,196
17 transactions · 13 stateful · 2026-06-10 00:23:27 UTC
Parallelism
82/100
Blocked
15%
Avg conflicts / tx
0.18
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #80,254,196 · 17 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
1w03w16w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x80afd9d9…57cf
0x065c9d…c394
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x01b0771a…2c50
0x065c9d…c394
2 touches
0 conflicts
0x0fa2dcc7…88f4
0x065c9d…c394
2 touches
0 conflicts
0x18b8bb2a…c31a
0x065c9d…c394
2 touches
0 conflicts
0x4410f2bc…6853
0x065c9d…c394
2 touches
0 conflicts
0x789084e6…d792
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
3 conflicts on slot 0x80afd9d9f2…3f57cf
Audit this contract →
← previous block·next block →recent activity