why2 reasons
mandatedestination_not_allowed
op 0 pays GDCPWV5WXYJ2VNOVH7GE3RXFYNXPQSFJM5J7JY2JJU53C34P7CAN6EBC, which is not in the allowlist
counterpartycounterparty_denied
GDCPWV5WXYJ2VNOVH7GE3RXFYNXPQSFJM5J7JY2JJU53C34P7CAN6EBC 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
- b3d119e3e78e091835ae6f7f4cc0c2daac5ca1d9eae74c786bd5a70b45d5c816
- request
- dab1b116ff9c340022e326a72963a7be985100dbe0eb70e3e075a2a1d23775e0
- transaction
- c3ff060ec091d6a145ed1a33d1014ad0dae09b28c795db2166e8915668e9706acomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 70082
the chainentry 70082
- sealed to the entry before
- fc1bbb36149f6bf53cf429223a17bc0bc2caf7c5cb4f7a912cebc4e2c370e5b8
- this leaf
- fcd4edfa28f2e1035877a1182e3f521216f9eea7e4c12b6ade857ad03d2704bf
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- sa9fnCv3z8Es0UMKeT0sKPhgF68vMantgkBtbymuS1qqoiTPrND2JRzGNS0/+FcMxLfNQYxEXwThPT8QrunPCg==