← previous blocknext block →recent activity
Analyzing
Block #80,339,999
16 transactions · 11 stateful · 2026-06-10 09:55:29 UTC
Parallelism
88/100
Blocked
18%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #80,339,999 · 16 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
1w02w13w010w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x7b9a42f7…7b88
0xa6afd3…d132
4 touches
1 conflict
0xe4afaa2f…3b69
0xa6afd3…d132
4 touches
1 conflict
0x487d2922…28b6
0x754704…b603
2 touches
1 conflict
0xef65bff3…7c9d
0x2a68ba…90c5
2 touches
0 conflicts
0x17bb6950…75d2
0x34b655…2a6f
2 touches
0 conflicts
0x1c7763f6…89be
0x34b655…2a6f
2 touches
0 conflicts
0x5d53448c…55b8
0x34b655…2a6f
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-WETH/USDC
1 conflict on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity