why2 reasons
mandatedestination_not_allowed
op 0 pays GD57AS7VG5LI3JJPZG4NMNJSTCVX2I4EUXAA4OGE5A3MHGEWAHZ3SO4A, which is not in the allowlist
counterpartycounterparty_denied
GD57AS7VG5LI3JJPZG4NMNJSTCVX2I4EUXAA4OGE5A3MHGEWAHZ3SO4A 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
- 38a5422182f934b2084c00edb2c64534df70bab24ae050d016283f1fba8a029e
- request
- f8b34de62e3e70242b0dada5ac698ebeffeccff5a903581fdf080fe5daa16629
- transaction
- f8bda3cca8471246ce16924e42d9947fbd66172f8d97ca97e3e7d33bae9d6d46computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 47683
the chainentry 47683
- sealed to the entry before
- b2c7e70affdf85b780c42b3e2e54940ea5b2f876d6f7b0bdc55a35221204550c
- this leaf
- 3e1bf45824d71d12087e2121e8c06aaf9cb6e8d595e6adabaeff7dd9f1f869fc
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- K45BdN7ZMU56vEN4mQSkJSGOTnPvRYBiWkuiwenR5ZyjctjG1kkUIgzQdXKixBrUG+i5IcQU/aimaFON3PD4DQ==