← previous blocknext block →recent activity

Analyzing

Block #82,755,693

24 transactions · 21 stateful · 2026-06-21 14:24:50 UTC

Parallelism

71/100

Blocked

43%

Avg conflicts / tx

0.92

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #82,755,693  ·  24 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

0xb3572c95…9c4a

0x2a68ba…90c5

8 touches
6 conflicts

0x14003d0c…8b42

0xa6afd3…d132

8 touches
6 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

6 touches
3 conflicts

0x5d46e6a0…5ed9

0x40c49f…2af0

4 touches
1 conflict

0xc824469a…6425

0x34b655…2a6f

4 touches
1 conflict

0xac3e4969…39e9

0x34b655…2a6f

4 touches
1 conflict

0x482471ad…122f

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

10 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity