why2 reasons
mandatedestination_not_allowed
op 0 pays GDMLNATQSSDOTBQLFBAQUBHJALUWN7XDAYRFHOWAKW3KMZK5G73DUNSK, which is not in the allowlist
counterpartycounterparty_denied
GDMLNATQSSDOTBQLFBAQUBHJALUWN7XDAYRFHOWAKW3KMZK5G73DUNSK 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
- 86f7c8ad00af3329f121f134bd423257ee7b02e718e99d7f4265cd90db4a75c7
- request
- b8b6fe84ae119abd40affe2eab686841db5faf961200a4d27381f2442b3a0a88
- transaction
- 0dbdba6ec75e95de48b8ba3ced5bc365b64cab899b1e56576608b7c9530aeb50computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 5751
the chainentry 5751
- sealed to the entry before
- 77f1ce5d3d2b36cf01a1ddb4083089cc4569f8fcc2a646156abbf53212a04eed
- this leaf
- 6a02a5afbff1dcbc6f04c367e51f28e609c7b0129d406f32021d450ae6697c71
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- ZHQyqIcPLkLJ7HIzwDgYz0GvfDEHsYHmVFD6cbLj0ozoGv9+N3zSm8WtGilMbadm3LvAu4MejrTmIEvtPjVmCQ==