why2 reasons
mandatedestination_not_allowed
op 0 pays GDZOBAR55MH2CYKI3E4R352UEMHIZ2Q5G7RAOYH3CJZDNJ56I24NHAJE, which is not in the allowlist
counterpartycounterparty_denied
GDZOBAR55MH2CYKI3E4R352UEMHIZ2Q5G7RAOYH3CJZDNJ56I24NHAJE 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
- a0e8dfa8fd65ac441439879145e7221f50b3feee7a754d331356298038278843
- request
- 58bbd36d42e36cb5ca7fdba62b6f3b04bda39e052028a7970a40b467e687222f
- transaction
- 19721743fb72d641b96b539fd57c7fe0e23f51281dd58bd36de0e07485b43e14computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 137
the chainentry 137
- sealed to the entry before
- fea87a7f1895a021cc2784781b939dfdfbeff1fe5be4c1b342297616e1194d3f
- this leaf
- a9f0848a93cef951fa1a995e97755b5e58c733ace0229d14905f5c684da5cc87
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 7YUDt+wjYXnfGwjBRkPwLbmwQ6RYNDSZM2ZIdrP5KYEVI0rR0mZU1cr9jXCjxeZY/cXsLhY4ROY6h7dxPpv8AQ==