← previous blocknext block →recent activity

Analyzing

Block #86,798,238

13 transactions · 11 stateful · 2026-07-10 07:58:53 UTC

Parallelism

77/100

Blocked

36%

Avg conflicts / tx

0.31

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #86,798,238  ·  13 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0xb4c35fcd…43ae

0xa6afd3…d132

4 touches
1 conflict

0x0b9f02c4…6fec

0x34b655…2a6f

4 touches
1 conflict

0x0c53719e…0366

0x34b655…2a6f

4 touches
1 conflict

0x1d826725…e975

0x34b655…2a6f

4 touches
1 conflict

0x482471ad…122f

0x34b655…2a6f

4 touches
1 conflict

0x4cdf55e1…0f2d

0x34b655…2a6f

4 touches
1 conflict

0xc3688185…9b36

0x34b655…2a6f

4 touches
1 conflict

0xc824469a…6425

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 0xb4c35fcde1…0943ae

← previous block·next block →recent activity