why2 reasons
mandatedestination_not_allowed
op 0 pays GDUV2ZENDHLEQ53XLCYA2ETD3RTRJQGHCM26GJGEE3KRKH5F7YBU5QJQ, which is not in the allowlist
counterpartycounterparty_denied
GDUV2ZENDHLEQ53XLCYA2ETD3RTRJQGHCM26GJGEE3KRKH5F7YBU5QJQ 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
- bab61819bcecc5578f73b3ba78f1b9e1f4b9e6bc9ee6fc6c6905cd9ba8a09777
- request
- dada1c2e118d863052bac230165c34c87d338250e9d288e13ad70dc20e564103
- transaction
- 07f3794ad2d25bb8a7c2b33638fcf696532f2a6f206603f5d8a0f807809b21c9computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 35500
the chainentry 35500
- sealed to the entry before
- da0de92fcfeb4892f17df31141febd070792dc999b98c024903c462f97775363
- this leaf
- 31821e35db6f8a26e104ba5233a8d4256789d1f1e151049438151d2bd802887d
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- O2GeKm4dmWy91b1tE0zFsaE7UsSoviNcHGudanZjhfyy0TP7ACVf/3e6zVu1KJv41sEfUQn2VdzgKdeJipXsAw==