why2 reasons
mandatedestination_not_allowed
op 0 pays GD42JKAWMZOJ3XDTLR6NPRPVM7AH7ISNFDLJ3CGVYJIXCEQ4XMJLKA4F, which is not in the allowlist
counterpartycounterparty_denied
GD42JKAWMZOJ3XDTLR6NPRPVM7AH7ISNFDLJ3CGVYJIXCEQ4XMJLKA4F 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
- 3738fc1641d58b8eaf4fdecd13cb34c496dd644be12b2f36b12882cd1fc8ec01
- request
- dd3ef2e8c44a194eccad4c7018cf24633c10bc8fbec063b143b31b5cfa456054
- transaction
- 057546f698ce26d78ddb615ba6c9dc587f49038d5b7557ccba1efe0f2286ba44computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 61317
the chainentry 61317
- sealed to the entry before
- 75a1c94e8cc6041bfb0290c80da2b49cf305a73f0d4a5ef415b7919f8043e7e4
- this leaf
- 1d260f853e74b565258983db2f4d07351d9fcedcda1c9688170da5d6eacb9367
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- hpUvuCLGIt6URCPltbunEHAVHFbSXdZZ9II4fJHSVphn0OTlb50AeOL/eVQlfwTgYJstIgop13jk8hVj2BNkDw==