why2 reasons
mandatedestination_not_allowed
op 0 pays GDVCPNGTEINWY5JI324GWXYF4ABMYUOO4NIUBDORK3ZNYZ7DNYXAMRN4, which is not in the allowlist
counterpartycounterparty_denied
GDVCPNGTEINWY5JI324GWXYF4ABMYUOO4NIUBDORK3ZNYZ7DNYXAMRN4 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
- baff0936e0ccb700ef3073edefdd8887a947c738c9e791dd5651b0aadbc53e4c
- request
- 2d684d6eb5e16772149b67ceb1614358fda03394c1d837740bbbb609ce76b48d
- transaction
- cb9c3e4d397b190266eb75986056da9775cbef33ffcf25b5530350ec42804326computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 34315
the chainentry 34315
- sealed to the entry before
- d64a021c5eaac0a071e4ab162707a00645bcf7854ef390444c5a0fc98775cb44
- this leaf
- a19abcdaef11bcc54974b066119038e147961d1f98dd2ef6108a874959220ad4
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Ky2IimZEjBf0kDpIenzoZhEtF478Nw+zrROdkGXXiRbZ1Dh4pBr02g+je0/OJiBxCCA1PCuidiinWxMEF6noAQ==