← previous blocknext block →recent activity
Analyzing
Block #80,315,242
12 transactions · 10 stateful · 2026-06-10 07:10:31 UTC
Parallelism
75/100
Blocked
20%
Avg conflicts / tx
0.25
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #80,315,242 · 12 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
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x21898044…a071
0x065c9d…c394
2 touches
0 conflicts
0x59ec617d…a074
0x065c9d…c394
2 touches
0 conflicts
0x8e3cecd8…18d4
0x065c9d…c394
2 touches
0 conflicts
0x9867ff70…4935
0x065c9d…c394
2 touches
0 conflicts
0xdd27805a…c41b
0x065c9d…c394
2 touches
0 conflicts
0xf45f06e2…3689
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