← previous blocknext block →recent activity
Analyzing
Block #80,220,143
10 transactions · 7 stateful · 2026-06-09 20:36:23 UTC
Parallelism
70/100
Blocked
29%
Avg conflicts / tx
0.3
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #80,220,143 · 10 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
1w02w13w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xeb97d867…50db
0x065c9d…c394
5 touches
3 conflicts
0xc9227c5f…1fd6
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x046a928e…0012
0x2a68ba…90c5
4 touches
1 conflict
0x3c63412b…c4df
0x065c9d…c394
3 touches
1 conflict
0xa225050a…5803
0x065c9d…c394
2 touches
0 conflicts
0xe9f6a7e4…f629
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 0xeb97d86721…7750db
Audit this contract →
← previous block·next block →recent activity