← previous blocknext block →recent activity

Analyzing

Block #80,300,120

21 transactions · 18 stateful · 2026-06-10 05:29:33 UTC

Parallelism

81/100

Blocked

39%

Avg conflicts / tx

0.38

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #80,300,120  ·  21 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0x7b9a42f7…7b88

0xa6afd3…d132

6 touches
3 conflicts

0xdf708ee7…1fcf

0xc8689a…ee79

4 touches
1 conflict

0x11e1fef0…f6ba

0x065c9d…c394

4 touches
1 conflict

0x40970e69…da50

0x69df8a…6292

4 touches
1 conflict

0x8cf3d245…1d0d

0x69df8a…6292

4 touches
1 conflict

0xb05cd4f5…73d0

0x69df8a…6292

4 touches
1 conflict

0xdb067026…9eb8

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