why2 reasons
mandatedestination_not_allowed
op 0 pays GDMSFAWDC5S5O2IU3PXZKRBMUOQDKB44NJHXH5PIEGXZSO7BLP2MJA5B, which is not in the allowlist
counterpartycounterparty_denied
GDMSFAWDC5S5O2IU3PXZKRBMUOQDKB44NJHXH5PIEGXZSO7BLP2MJA5B 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
- 7b15f0664225666be318c7a7684532cf90e3a51418347e1ddf438d4ed45be4d3
- request
- 78d47e2e5e7270b94740b43d599a7bec60af63881f8bdc9348b449eced71e3d5
- transaction
- d1672686ce122e978830d764f9a5bc7f4fced629c3996d7e64940f27860c7fe2computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 36105
the chainentry 36105
- sealed to the entry before
- 20c1c358e31591be310fc825b3c2c78251ad169b4ec7c57e0c344b6a9a01eb18
- this leaf
- 53e6325b21c2123b1712412298b0b902fefb35aa7624265643d130fbb5a42277
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- clEAo9/M6mf3IcVMn+BCfzqcC0xCELqehB7KsIb1Cc2zettC2HMEarPaFIBiAzODy2YaJtAt2q1OWZ3C3TuCCQ==