why2 reasons
mandatedestination_not_allowed
op 0 pays GDQQUEX6IBIJPQGNHPRV3ZPG2JP4F7F7V3QPR2S6PE7W7CGYMLTBB6A4, which is not in the allowlist
counterpartycounterparty_denied
GDQQUEX6IBIJPQGNHPRV3ZPG2JP4F7F7V3QPR2S6PE7W7CGYMLTBB6A4 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
- b8b202e9048ee9fcd50623b8184c57fa3d6c2eb846dec55ec06a9ddcdbac25c7
- request
- fac0497a37f5da965677b95b5aaba69b3131829dde8f49e0e7ad4436b2193924
- transaction
- 0e49480db24c77505a3d3c65b5bd6ee90152efd16fcf1f17a9f8967ecb8c5c14computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 49889
the chainentry 49889
- sealed to the entry before
- b0b4959009970a7440c04f02a87b88600babe5ac89160d873a8d9524685e5854
- this leaf
- 3c54a8a710f00a1ccc2c1e8c691f337e64edd5ae1f4b01d4f10e618a1a4ec748
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- PPHBphH/C8aAZKcymR7S208s+rd+zHiTWfqIsMsmXAAEgo5sOV3dickUNl6pOFq9Y9IbUCFCccLjW4k35RcKCQ==