why2 reasons
mandatedestination_not_allowed
op 0 pays GDY5YWCM2PVZQK7EMJDQUNXU5XZ5QXYPPVA2NNOMJONH34ZXEA4EVXHQ, which is not in the allowlist
counterpartycounterparty_denied
GDY5YWCM2PVZQK7EMJDQUNXU5XZ5QXYPPVA2NNOMJONH34ZXEA4EVXHQ 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
- b0b173aac147c0d03eca694fcb00c6c856eeceb9d69358eaa75ce8153662f872
- request
- f3d569f31bd27ed90931358548d1a7708c2bfd0b8da15d1ba02d4a6f6119c2bc
- transaction
- dba882e7f6503c144cf62ce343889ba8f579ed1130cfc1f81eca2c7d38cbfee2computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 887
the chainentry 887
- sealed to the entry before
- a35a83913e1c392cc9449d719b1320dbba843c93fd2227f34149283f16dc4941
- this leaf
- ed60ecfc91a14083c36e722c5a944edcc4c97db35e5a6f5a0ae2c222257cf719
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- uIr3sFAhZlleCJh7zQHWVcQOqCjL98YANHo5fX5GxgiwQj4hUHgoNcgIUQMYAI1JrRTdlvVVt5HgW2ZmZbK7CQ==