why2 reasons
mandatedestination_not_allowed
op 0 pays GB76ZSDUUCWSAXTX7EAC34UBXTZXP2ASC4EIIUT6APTA33TPLM5JB4X4, which is not in the allowlist
counterpartycounterparty_denied
GB76ZSDUUCWSAXTX7EAC34UBXTZXP2ASC4EIIUT6APTA33TPLM5JB4X4 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
- 0819449dce97940e71f30d5fdee57b10aa503bd9f62f80566f1f7815633d8e2b
- request
- 2c0da15a0e3c81a820f13d1b4714093da8522998967c0c1278d8104450e6e5ee
- transaction
- 749b439c864b72ce58daeee73699b5d8f7bf376b06b38d7040ff25328da0a97bcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 4955
the chainentry 4955
- sealed to the entry before
- f1f79a785a75a244081aeec4440703e08266e5a6ea55035b7e8b9ac7b42fff75
- this leaf
- c0dce5a131f9862f9e467025092dc094bd1e47b22a8d1375e5fa811fe129ba77
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- zpZCunihPdz5f57PQUfn2+tuhnqRGcsAROyXwqnoRyL8J5SorIP2mdRT696mw3IVOkybkBnUCgaPBXdMoiCjCw==