← previous blocknext block →recent activity

Analyzing

Block #80,826,686

29 transactions · 21 stateful · 2026-06-12 16:00:54 UTC

Parallelism

83/100

Blocked

38%

Avg conflicts / tx

0.45

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #80,826,686  ·  29 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

0x9e20cccf…19cc

0xa6afd3…d132

8 touches
6 conflicts

0x00000000…002b

0x1b6862…e19c

8 touches
6 conflicts

0x928d6b23…5370

0x1b6862…e19c

8 touches
6 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…0012

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…0013

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…003d

0xa6afd3…d132

8 touches
6 conflicts

0x565818b0…80a3

0xa6afd3…d132

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

6 conflicts on slot 0x9e20cccfee…8c19cc

← previous block·next block →recent activity