← previous blocknext block →recent activity

Analyzing

Block #82,759,934

26 transactions · 18 stateful · 2026-06-21 14:53:05 UTC

Parallelism

88/100

Blocked

39%

Avg conflicts / tx

0.35

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #82,759,934  ·  26 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0x08913286…f0df

0x34b655…2a6f

6 touches
3 conflicts

0x0d996440…df68

0x34b655…2a6f

4 touches
1 conflict

0x21e43e72…d2f6

0x34b655…2a6f

4 touches
1 conflict

0x482471ad…122f

0x34b655…2a6f

4 touches
1 conflict

0x4de3018c…a70d

0x34b655…2a6f

4 touches
1 conflict

0x4f4bdabd…ffba

0x34b655…2a6f

4 touches
1 conflict

0x664bf99e…0a8c

0x34b655…2a6f

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