← previous blocknext block →recent activity
Analyzing
Block #80,316,094
16 transactions · 13 stateful · 2026-06-10 07:16:11 UTC
Parallelism
81/100
Blocked
15%
Avg conflicts / tx
0.31
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #80,316,094 · 16 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
1w03w04w15w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x21898044…a071
0x065c9d…c394
6 touches
3 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x513e200b…e0a1
0x065c9d…c394
2 touches
0 conflicts
0x5b102744…3894
0x065c9d…c394
2 touches
0 conflicts
0x7bfd6087…8c30
0x065c9d…c394
2 touches
0 conflicts
0xd0de3ae7…fd2c
0x065c9d…c394
2 touches
0 conflicts
0xedcc4308…7d2c
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 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity