why2 reasons
mandatedestination_not_allowed
op 0 pays GBYFOWCV2N4ALYPTWCQBN4RVTJ2OEWIKNCFD2XP6TFVKV2NANKOKBTQY, which is not in the allowlist
counterpartycounterparty_denied
GBYFOWCV2N4ALYPTWCQBN4RVTJ2OEWIKNCFD2XP6TFVKV2NANKOKBTQY 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
- d1f6dd792c818f2f4275edf8db2c3ebcf683a0f93d2df005d0cd6161f186105b
- request
- 6e11c2cb87a8c8e8330709e195810b107ba33528685c369931c3774f2994befb
- transaction
- 4693b3e5b2024cb90ff5968e175b28c926905162147a006bd33a0d2816fc6978computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 41006
the chainentry 41006
- sealed to the entry before
- 2a8a22e7f5707f7c601047e13648c07c0e58c8d977cf5b5af532bf237c2fac3a
- this leaf
- 298925736091cf477ac91dd42762cf2ab00c79fec47cad666e1909b9b5f1779e
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- rh/jSnpnc51CLNGeZyRNpVu3m74q4QYiBYs4XCgPoXk2ITEGOFrbNnINLZavh6OqsNmifbgqMF1UveEjw7E5Ag==