why2 reasons
mandatedestination_not_allowed
op 0 pays GDGYCM27OMY5UEIHR4OOQGROXBKI7BYJ232ZSHNZJYHOZXLT7NYX3JBY, which is not in the allowlist
counterpartycounterparty_denied
GDGYCM27OMY5UEIHR4OOQGROXBKI7BYJ232ZSHNZJYHOZXLT7NYX3JBY 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
- 8779dceb047e02ea56c0f644c8ac6251c0631994e3ce640d50f7cae59e22c96c
- request
- fb3096b695bf891906a2d9500e8a8fbcf98ca732e5ecbcb66d770aa77f1570ba
- transaction
- e500facdbe27ae1d3fef05e471cd37de1bc828927536833ddf702c24d1f92459computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 19924
the chainentry 19924
- sealed to the entry before
- e0a70ddce2584dbb1800dc4260e28936d4974f475c08aaea56472c0799fc778d
- this leaf
- 7ae3dafe1cfd9a27331c437e579e6d678812475fa069029e7b5873967e721476
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- PAPEPdgSYTa3Kzo0U0wHS5a5baxocNWPKuQACQ27CoNqxhfKBSOzqPmaCn3lAXqsQKZmFkfNNNcz8IB86uLnAQ==