← previous blocknext block →recent activity

Analyzing

Block #85,567,246

25 transactions · 19 stateful · 2026-07-04 15:00:07 UTC

Parallelism

84/100

Blocked

37%

Avg conflicts / tx

0.52

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #85,567,246  ·  25 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

8 touches
6 conflicts

0xfaef08b1…0696

0x34b655…2a6f

8 touches
6 conflicts

0x2c8bf7d9…3cc7

0xc8689a…ee79

8 touches
6 conflicts

0xb4c35fcd…43ae

0xa6afd3…d132

8 touches
6 conflicts

0x89750670…2dea

0xa6afd3…d132

8 touches
6 conflicts

0x3a6290da…e683

0x34b655…2a6f

8 touches
6 conflicts

0x43ffd8bd…0d0c

0x34b655…2a6f

8 touches
6 conflicts

0x664bf99e…0a8c

0x34b655…2a6f

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 0x0000000000…00003d

← previous block·next block →recent activity