← previous blocknext block →recent activity

Analyzing

Block #85,772,689

14 transactions · 13 stateful · 2026-07-05 13:49:20 UTC

Parallelism

86/100

Blocked

31%

Avg conflicts / tx

0.36

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #85,772,689  ·  14 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

0x66f473d3…2d03

0xa6afd3…d132

4 touches
1 conflict

0x7fe4a652…079b

0x34b655…2a6f

4 touches
1 conflict

0xc824469a…6425

0x34b655…2a6f

4 touches
1 conflict

0xcdc1731c…b91a

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0xda46a376…f6a6

0x34b655…2a6f

4 touches
1 conflict

0xdc95131b…ae64

0x34b655…2a6f

4 touches
1 conflict

0xefcdf197…96a2

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 0x66f473d356…fb2d03

← previous block·next block →recent activity