<p></p>
<p>I agree that bisq should allow (even encourage) use of an user's own blockchain explorer. However, hard coding in one company's implementation (explorer/url) isn't the right way to do it.</p>

<p style="font-size:small;-webkit-text-size-adjust:none;color:#666;">—<br />You are receiving this because you are subscribed to this thread.<br />Reply to this email directly, <a href="https://github.com/bisq-network/bisq/pull/4634#issuecomment-716811667">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/AJFFTNSVECSG2SZSJCK5YI3SMXNPLANCNFSM4SN2AFCQ">unsubscribe</a>.<img src="https://github.com/notifications/beacon/AJFFTNVMWDJJPDFBOWOBC5LSMXNPLA5CNFSM4SN2AFC2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOFK423EY.gif" height="1" width="1" alt="" /></p>
<script type="application/ld+json">[
{
"@context": "http://schema.org",
"@type": "EmailMessage",
"potentialAction": {
"@type": "ViewAction",
"target": "https://github.com/bisq-network/bisq/pull/4634#issuecomment-716811667",
"url": "https://github.com/bisq-network/bisq/pull/4634#issuecomment-716811667",
"name": "View Pull Request"
},
"description": "View this Pull Request on GitHub",
"publisher": {
"@type": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
}
]</script>