why2 reasons
mandatedestination_not_allowed
op 0 pays GDZTAVVCERX4HJNFM6CGF4QQ5RO7PTVAMXKYPF2LTXM2AORRT3OMQACR, which is not in the allowlist
counterpartycounterparty_denied
GDZTAVVCERX4HJNFM6CGF4QQ5RO7PTVAMXKYPF2LTXM2AORRT3OMQACR 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
- 0137a7a88a6d17d09f6ffcea80a1b8b7786080fe5d0fe21798964fc9c09bab74
- request
- 5a75bff005abd9ac26b0a1fa6213616784cb3fe43ba507df7705af2d1b61ab18
- transaction
- 25f83acc150d609e8fa91e80fd9917ef448c15bcfcfe946918bc998c8291ea2fcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 63030
the chainentry 63030
- sealed to the entry before
- 60714ea0d4e813ff1bd3f3b6c3e5f60965f47a60dab868e7c8a8dbd526944d1c
- this leaf
- 640d21122c9c5aa1c27642f90e7ca004246699eb29dcbad79f1f3682f72d0dc8
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- XBXboXZf8+5lxSs8bAHTPYdpPAzeBuUXH2RvDuEAb8HJodPDkvgiRCy1JC0w8dR8I1xEKKsxLOa0rZsXIVPhBw==