why2 reasons
mandatedestination_not_allowed
op 0 pays GDJNGC5ZLUXAO74BW2YZOT4QCVS7UIXLBBMTD5UMVP67RO2722RNGOZZ, which is not in the allowlist
counterpartycounterparty_denied
GDJNGC5ZLUXAO74BW2YZOT4QCVS7UIXLBBMTD5UMVP67RO2722RNGOZZ is on the screening list: you placed this account on the screening list for this run
what it was decided fromfingerprints
- rule compiled from it
- e7ffa726c11c1b4363e9026610824dd8440b0ca17cae9f0094e8b6a1d00caff3
- request
- f6b8e12d081264b27eba998e73c056bbd1cf7c4fb6388c3463ee783877f05564
- transaction
- 50907ef48bccd87b961772e545591d4761ecfd8ac5b69f38a1d4c7eb6701aa13computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 38510
the chainentry 38510
- sealed to the entry before
- b684ebcd795e9cafdeb29a203869087c5735287737787cfadaf98e88745d762a
- this leaf
- 3453679a57dc8176d584cbc4f84f00ce144f31d876fc0692c49644ff5df7b35f
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 4Ek9UAJyMyZfsdshOHurM+4qZR+dYTYvkLDsl2GE8ZHHjeMtlGzPu37lER6FQ87YCIkip4SlykvYUiGFf/dhAA==