why2 reasons
mandatedestination_not_allowed
op 0 pays GCXZDHB5MGSMKEBE5VK5JFNT7YQA46I6RQ66EBY4FNQPITKNLJKIOSY5, which is not in the allowlist
counterpartycounterparty_denied
GCXZDHB5MGSMKEBE5VK5JFNT7YQA46I6RQ66EBY4FNQPITKNLJKIOSY5 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
- 116c528132255d0f6a02cf6244636c97ebb3c685911362613e0b5a83f577ce39
- request
- f8491f1889f306af06c8cc3104e8c8e0f019f8b273af3d46b10539ff0aa0181b
- transaction
- 0c78fe2ba86d6361fb8f4d23c68ff115a4fcb15039647d96c7243f5c62109faecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 65153
the chainentry 65153
- sealed to the entry before
- 4c4d08f40284af172e858c7a741003681e59c10e637ae7025053ccf65f8192ef
- this leaf
- 050ddc6663d37298665a2b5e05a82c8142d2c94e0fc66291eeb9f7c0b83bcd95
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 85Y+EMcNJsMFT84byH/FMZ7hcKO7KiUNqUe8YxorBeacPHFZdIbVhGTigG96JLI4RQv4KovFsOMZh61u3/TrCQ==