why2 reasons
mandatedestination_not_allowed
op 0 pays GDYCREBDR3WZW2QVAZU2E3EFWWJYRATPRQ5GGLBUGY4EJL74ASUT5HLH, which is not in the allowlist
counterpartycounterparty_denied
GDYCREBDR3WZW2QVAZU2E3EFWWJYRATPRQ5GGLBUGY4EJL74ASUT5HLH 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
- cf5d70553e5878c57aac8dec14e67d82c3d11c08f046522cbca89ac495db5451
- request
- aee6cc7d94bb8b51f501c12e37570a69c5dc2bb91a37b6861420bfd1b3336720
- transaction
- 9c0d7363d1901193af9d79938f4b68c66fd63fcc8e452603e5205591deb5311dcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 34026
the chainentry 34026
- sealed to the entry before
- 04c1857aeeae6bff9f8b9be8460a392f1733c9c85f7c6468f4a9b509ac88122d
- this leaf
- b129611430a59b3f2f238051ab18fae4cf0b68f175d89ab6548266b9f57cd41d
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- K+v8mu1NWXjb1s0erwaRUrQFUPlX//yiIenm+k3HhSsQRzNks/LxDlHWQik68npd6EuobWmjdRd29FPRuT8WDA==