← previous blocknext block →recent activity
Analyzing
Block #80,327,942
10 transactions · 9 stateful · 2026-06-10 08:35:10 UTC
Parallelism
80/100
Blocked
22%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #80,327,942 · 10 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w16w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf137ceba…7984
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x0c531fa3…69c0
0x065c9d…c394
2 touches
0 conflicts
0x5879cb51…40eb
0x065c9d…c394
2 touches
0 conflicts
0x5b134698…5226
0x065c9d…c394
2 touches
0 conflicts
0xef18cedb…f598
0x065c9d…c394
2 touches
0 conflicts
0x01e7b865…6e6d
0x188d58…ea8e
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 0xf137ceba01…fa7984
Audit this contract →
← previous block·next block →recent activity