← previous blocknext block →recent activity

Analyzing

Block #80,327,944

20 transactions · 15 stateful · 2026-06-10 08:35:10 UTC

Parallelism

75/100

Blocked

47%

Avg conflicts / tx

0.45

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #80,327,944  ·  20 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0xe41f8863…29a4

0xa6afd3…d132

6 touches
3 conflicts

0x13a54fa2…5ae3

0x2a68ba…90c5

6 touches
3 conflicts

0x00000000…003d

0xa6afd3…d132

6 touches
3 conflicts

0x158accef…4c74

0xa6afd3…d132

6 touches
3 conflicts

0x44d7acbf…e67b

0x1b6862…e19c

4 touches
1 conflict

0xdf708ee7…1fcf

0xc8689a…ee79

4 touches
1 conflict

0x0d622e34…0000

0x681e90…ae09

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 0xe41f886384…3929a4

← previous block·next block →recent activity