← previous blocknext block →recent activity

Analyzing

Block #82,328,359

21 transactions · 17 stateful · 2026-06-19 14:49:52 UTC

Parallelism

76/100

Blocked

41%

Avg conflicts / tx

0.76

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #82,328,359  ·  21 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

0x66c5e348…51d0

0xa6afd3…d132

8 touches
6 conflicts

0x00000000…003d

0xa6afd3…d132

8 touches
6 conflicts

0x1b3114cd…5e2d

0xa6afd3…d132

6 touches
3 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

6 touches
3 conflicts

0x00000000…0013

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0015

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0019

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0029

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

6 conflicts on slot 0x66c5e3484c…3451d0

← previous block·next block →recent activity