← previous blocknext block →recent activity

Analyzing

Block #80,604,651

19 transactions · 18 stateful · 2026-06-11 15:20:08 UTC

Parallelism

84/100

Blocked

39%

Avg conflicts / tx

0.47

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #80,604,651  ·  19 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

- write/write- - read/write

x = tx position · y = wave (depth)

Hot storage slots

Contention

0x00000000…003d

0xa6afd3…d132

6 touches
3 conflicts

0x0d622e34…0000

0x681e90…ae09

6 touches
3 conflicts

0x13a54fa2…5ae3

0x2a68ba…90c5

4 touches
1 conflict

0x36d366fe…7adc

0xa6afd3…d132

4 touches
1 conflict

0xdf708ee7…1fcf

0xc8689a…ee79

4 touches
1 conflict

0x90f07a4f…d932

0x34b655…2a6f

4 touches
1 conflict

0x56a919c4…ab49

0xee8c0e…1242

4 touches
1 conflict

0x40970e69…da50

0x69df8a…6292

4 touches
1 conflict

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

3 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity