why2 reasons
mandatedestination_not_allowed
op 0 pays GDGTEUGOPBEE4XRVTJVXZ2CSTPSCY567OFTNGDBC6TGINLP4OSE64VV2, which is not in the allowlist
counterpartycounterparty_denied
GDGTEUGOPBEE4XRVTJVXZ2CSTPSCY567OFTNGDBC6TGINLP4OSE64VV2 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
- a8abff7137fb26c08981fd7a9d10d5b3b21a4557560c8a373ac07b710aafb514
- request
- 17e11bd20618142c7cca28decd33d1dd8144adc15bab477e84e0e288ee54c4fa
- transaction
- 7c43f80eb8803ae38f6009f20ee4346b9eb18380b92ecf8f205442cc62e4b669computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 51379
the chainentry 51379
- sealed to the entry before
- 5d3b84708391d15446fe0f90f2e8c62558deb33a267efc895a9b3389465e5fef
- this leaf
- 4f1e62035f0a452278f2926be946ee813f32d388878256bac57f82ac188262a3
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- xnN7t+jQ9AIuVEAjnFHQMdD6POxmk5JFy5Vgw3BaHnVgxMKQz14SUPl2iFxJzUGBG940moB5KhwOQ0MequmCAQ==