# Unable to decode output address **URL:** \ **Category:** Support\ **Created:** [February 28, 2018, 8:46pm UTC](https://bisq.community/t/unable-to-decode-output-address/4909 "2018-02-28T20:46:25Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![TitoSP](https://bisq.community/user_avatar/bisq.community/titosp/32/1466_2.png) [@TitoSP](https://bisq.community/u/TitoSP)\ **Post date:** [February 28, 2018, 8:46pm UTC](https://bisq.community/t/unable-to-decode-output-address/4909/1 "2018-02-28T20:46:25Z")
Unable to decode output address when I check in blockchain the deposit transaction ID It has been like this for hours now… what can I do??? c2b27966cc92382089de090f261d7555b57ee7769b87872dfebc3d75d720bd88 ---
**Author:** ![alexej996](https://bisq.community/user_avatar/bisq.community/alexej996/32/491_2.png) [@alexej996](https://bisq.community/u/alexej996)\ **Post date:** [February 28, 2018, 9:18pm UTC](https://bisq.community/t/unable-to-decode-output-address/4909/2 "2018-02-28T21:18:38Z")
It is a multisig transaction, so don’t worry about blockchain explorers not showing all the info, they are not used to that, but the transaction is perfectly valid and that is why they show it in the first place. As for the waiting time, fees might have jumped rapidly and blocks might be full at the moment. I guess the simplest solution is just to wait patiently, it should get confirmed eventually, but fee estimation is a tricky business. ---
**Author:** ![ManfredKarrer](https://bisq.community/user_avatar/bisq.community/manfredkarrer/32/26_2.png) [@ManfredKarrer](https://bisq.community/u/ManfredKarrer)\ **Post date:** [March 1, 2018, 1:50am UTC](https://bisq.community/t/unable-to-decode-output-address/4909/3 "2018-03-01T01:50:08Z")
The second output is a OP\_RETURN where we store the hash of the trade contract. It is normal that blockexplorers cannot show that data.