← previous blocknext block →recent activity
Analyzing
Block #80,292,628
10 transactions · 10 stateful · 2026-06-10 04:39:42 UTC
Parallelism
70/100
Blocked
20%
Avg conflicts / tx
0.3
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #80,292,628 · 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
1w02w13w04w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0xfb64e9ec…34fd
0x2a68ba…90c5
3 touches
1 conflict
0x4c5575a2…45c4
0x065c9d…c394
2 touches
0 conflicts
0x66c21f54…af0e
0x065c9d…c394
2 touches
0 conflicts
0x9f97d127…a8de
0x065c9d…c394
2 touches
0 conflicts
0xc965d190…81f3
0x065c9d…c394
2 touches
0 conflicts
0x00000000…0000
0x24b18e…3301
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