← previous blocknext block →recent activity

Analyzing

Block #85,531,372

18 transactions · 18 stateful · 2026-07-04 11:01:16 UTC

Parallelism

89/100

Blocked

11%

Avg conflicts / tx

0.11

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #85,531,372  ·  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

0xb68e226d…c054

0xa6afd3…d132

4 touches
1 conflict

0x006c3b86…59a9

0x34b655…2a6f

4 touches
1 conflict

0x05edf2cf…ac3c

0x34b655…2a6f

4 touches
1 conflict

0x170e4e4c…2b90

0x34b655…2a6f

4 touches
1 conflict

0x213a54fa…c85f

0x34b655…2a6f

4 touches
1 conflict

0x295e0f1a…0354

0x34b655…2a6f

4 touches
1 conflict

0x3860e0d3…b270

0x34b655…2a6f

4 touches
1 conflict

0x548145a9…cfce

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 0xb68e226d12…aac054

← previous block·next block →recent activity