← previous blocknext block →recent activity

Analyzing

Block #86,685,106

17 transactions · 14 stateful · 2026-07-09 19:23:25 UTC

Parallelism

88/100

Blocked

29%

Avg conflicts / tx

0.24

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #86,685,106  ·  17 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

0x1c03f81f…b303

0x34b655…2a6f

4 touches
1 conflict

0x1c03f81f…b304

0x34b655…2a6f

4 touches
1 conflict

0x453f53a8…e541

0x34b655…2a6f

4 touches
1 conflict

0x4bd1d7fb…b907

0x34b655…2a6f

4 touches
1 conflict

0x6e90b9b1…dca8

0x34b655…2a6f

4 touches
1 conflict

0x7f5b2c1d…0e7f

0x34b655…2a6f

4 touches
1 conflict

0x8d73d60f…c99c

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