why2 reasons
mandatedestination_not_allowed
op 0 pays GDQ2L63HTJ4CGSYO5E5DQ2YWCX6XMYARUNDZW5XQ24BEI23TNPKI3DMS, which is not in the allowlist
counterpartycounterparty_denied
GDQ2L63HTJ4CGSYO5E5DQ2YWCX6XMYARUNDZW5XQ24BEI23TNPKI3DMS 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
- 85e4956b2e98ea368cf88b65efd94f3c29b7d7e5ffba7402512174e563d3e892
- request
- 62c92cfec6c2a662f0b2518902c104d8bf8efbf2d679cb969a3007c1d0155ee8
- transaction
- 85ae6fa2f6d177d0a04ed9e886d35c80442bb89bb69a1c895bea5b9ef39de861computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 19213
the chainentry 19213
- sealed to the entry before
- fbb10142843403e6deb5cfecb966d9c1a4d6e9c6add06c675435c233021f3b87
- this leaf
- ab0cefd681ebdcab4b697984f05410ff3cf1a6f93042c19c1d5e5d3d5cd72f3d
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- w6eCl6B4Cgsfizieb4j8vpmW0DwMrRO/F47WxOmldhEjJpkYIVW8y5PzFq2VLgHdcWBXMfWAXt/t+SmxWnhWAQ==