← previous blocknext block →recent activity

Analyzing

Block #85,576,654

24 transactions · 18 stateful · 2026-07-04 16:02:49 UTC

Parallelism

83/100

Blocked

39%

Avg conflicts / tx

0.38

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #85,576,654  ·  24 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0x202c03eb…cf33

0xa6afd3…d132

6 touches
3 conflicts

0xc7a15219…7745

0xa6afd3…d132

6 touches
3 conflicts

0x00000000…003d

0xa6afd3…d132

6 touches
3 conflicts

0xefcdf197…96a2

0x34b655…2a6f

6 touches
3 conflicts

0x6fc24f20…f3c7

0x34b655…2a6f

4 touches
1 conflict

0xbfc5a752…ea85

0x34b655…2a6f

4 touches
1 conflict

0xc824469a…6425

0x34b655…2a6f

4 touches
1 conflict

0x00000000…0002

0x04fdea…47d7

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

3 conflicts on slot 0x202c03eb74…a7cf33

← previous block·next block →recent activity