why2 reasons
mandatedestination_not_allowed
op 0 pays GD6YGM5TI5FDAZHVDRMLRXX3UFRGZZK7OASCLAHYD3R4KLFQVA7EPNLC, which is not in the allowlist
counterpartycounterparty_denied
GD6YGM5TI5FDAZHVDRMLRXX3UFRGZZK7OASCLAHYD3R4KLFQVA7EPNLC 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
- 0be70b4288eea16f072934d3612f224e07b56f0ffd9c91a901d521f666af26df
- request
- 85a583c2a74da5f3c4cadf231ba0363aff8034f3e4b5b65d38007b1150b0e439
- transaction
- 72883d4930e7bba0c3880a9f7c1c7a57d7efeb4d09969a4c1430e4886ca3a057computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 26464
the chainentry 26464
- sealed to the entry before
- 523c9f45559c240f1d16202c31b663c0c717ebd1ef7dbd05911fb5598e57dc6f
- this leaf
- e5c0910f488328518e53016397fc43413d79e487cfcb51a370d11fb37f18b992
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- qF0ZDqKD8VxxYUC031nCmoM4tAouNfHD0eaRq50tR1T/RTitfJCMKxIeeaeX107OUPeMKN+Daeb+RrvIdlTqCg==