← previous blocknext block →recent activity

Analyzing

Block #85,763,581

12 transactions · 11 stateful · 2026-07-05 12:48:41 UTC

Parallelism

83/100

Blocked

18%

Avg conflicts / tx

0.17

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #85,763,581  ·  12 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

0x652bc0f0…6faf

0x34b655…2a6f

4 touches
1 conflict

0x6f7a92ed…5651

0x34b655…2a6f

4 touches
1 conflict

0x94f5fc74…a10d

0x34b655…2a6f

4 touches
1 conflict

0x9a3068dd…18f0

0x34b655…2a6f

4 touches
1 conflict

0x9a3068dd…18f1

0x34b655…2a6f

4 touches
1 conflict

0xb6994e8b…b528

0x34b655…2a6f

4 touches
1 conflict

0xc978dec7…e3d6

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