why2 reasons
mandatedestination_not_allowed
op 0 pays GB3YSIBVNBEOL3PYEHJLCJEOWV5BKM24AM3BNQW73B2XR4JAALSTVL4E, which is not in the allowlist
counterpartycounterparty_denied
GB3YSIBVNBEOL3PYEHJLCJEOWV5BKM24AM3BNQW73B2XR4JAALSTVL4E 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
- 1dc868a9bd21862de8bb4f228d03487d18fc6ff5d32b1c6d62a7c4576a8d7bba
- request
- d1f5b37f0c8474de8b925124f74cf777ebba8cb2a95bd28d2c8b8611431b36f4
- transaction
- dcbc3dcf1ac8f583055c04c27bc03feceefb0442f6d5c36862a776cb38607217computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 17951
the chainentry 17951
- sealed to the entry before
- a4a348048aa38a0007455608de29fbb3cec9e4a45690ce8274e38aa4dfbfbdef
- this leaf
- fcb9e38d0c7a73e8f9a5de9a6d06c8221248c1f9c3bd0689ddbf4d963c65cbac
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- sp5bMJUW3TIM4cA4DMXcEl5Z8sYoFGQVbqA5QkGsH4bzmyFLWg2QNq2B2mqVxsRQK/t/ajb9pgYj09pxXGDwCA==