← previous blocknext block →recent activity

Analyzing

Block #80,573,217

28 transactions · 24 stateful · 2026-06-11 11:50:02 UTC

Parallelism

68/100

Blocked

42%

Avg conflicts / tx

1.32

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #80,573,217  ·  28 txs across 9 waves  ·  depth 9
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

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

14 touches
21 conflicts

0x9e20cccf…19cc

0xa6afd3…d132

12 touches
15 conflicts

0x565818b0…80a3

0xa6afd3…d132

12 touches
15 conflicts

0xdb067026…9eb8

0x69df8a…6292

8 touches
6 conflicts

0x40970e69…da50

0x69df8a…6292

8 touches
6 conflicts

0x8cf3d245…1d0d

0x69df8a…6292

8 touches
6 conflicts

0xb05cd4f5…73d0

0x69df8a…6292

8 touches
6 conflicts

0x13a54fa2…5ae3

0x2a68ba…90c5

8 touches
6 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

21 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity