← previous blocknext block →recent activity

Analyzing

Block #80,248,782

28 transactions · 19 stateful · 2026-06-09 23:47:25 UTC

Parallelism

75/100

Blocked

53%

Avg conflicts / tx

0.82

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #80,248,782  ·  28 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

10 touches
10 conflicts

0x13a54fa2…5ae3

0x2a68ba…90c5

10 touches
10 conflicts

0x179fe783…6945

0xa6afd3…d132

8 touches
6 conflicts

0xdf708ee7…1fcf

0xc8689a…ee79

6 touches
3 conflicts

0x7531e9d9…196d

0xa6afd3…d132

5 touches
3 conflicts

0x00000000…002f

0x1b6862…e19c

4 touches
1 conflict

0xd9f18d9a…141d

0x1b6862…e19c

4 touches
1 conflict

0xec85b41e…7c97

0x1b6862…e19c

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

10 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity