← previous blocknext block →recent activity

Analyzing

Block #85,918,354

18 transactions · 15 stateful · 2026-07-06 05:59:37 UTC

Parallelism

89/100

Blocked

27%

Avg conflicts / tx

0.28

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #85,918,354  ·  18 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

4 touches
1 conflict

0xafd867b7…2b2d

0x34b655…2a6f

4 touches
1 conflict

0xafd867b7…2b2e

0x34b655…2a6f

4 touches
1 conflict

0xc824469a…6425

0x34b655…2a6f

4 touches
1 conflict

0xea1b8c07…b969

0x34b655…2a6f

4 touches
1 conflict

0xec2e0314…c9de

0x34b655…2a6f

4 touches
1 conflict

0xf719d99a…d8be

0x34b655…2a6f

4 touches
1 conflict

0xff196840…a453

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

1 conflict on slot 0x0000000000…00003d

← previous block·next block →recent activity