← previous blocknext block →recent activity
Analyzing
Block #80,216,538
13 transactions · 11 stateful · 2026-06-09 20:12:25 UTC
Parallelism
69/100
Blocked
27%
Avg conflicts / tx
0.23
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #80,216,538 · 13 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
1w02w13w25w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x6cf4c1b0…1422
0x065c9d…c394
4 touches
1 conflict
0x319a615a…02e8
0x065c9d…c394
3 touches
1 conflict
0xdff23e16…84b1
0x065c9d…c394
3 touches
1 conflict
0x9d3f2124…725b
0x2a68ba…90c5
2 touches
1 conflict
0xb182933f…46ed
0x754704…b603
2 touches
1 conflict
0x729c91b8…9538
0x188d58…ea8e
2 touches
0 conflicts
0x17606ba6…1b6e
0x754704…b603
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