why2 reasons
mandatedestination_not_allowed
op 0 pays GD4M6APRJAKM5LCZILVRGBX2SISQKL7HXNUVV7LPAYNQ3IXHIH2FBTFF, which is not in the allowlist
counterpartycounterparty_denied
GD4M6APRJAKM5LCZILVRGBX2SISQKL7HXNUVV7LPAYNQ3IXHIH2FBTFF 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
- f0a7277671cb7d1a0ee3f88f4c7c413138d6ff9c86aa34a0bd88dc45c7803cd7
- request
- eaa04fc26b2ff1b0e4f507ec66288ca776050ee3cc76fad8227b6ea022478308
- transaction
- 6f825390482195a3ebb7331cc69c14bd9c8658bcf2d4bd0ae1697003abdf7cc9computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 75972
the chainentry 75972
- sealed to the entry before
- 41695e7132a1d71e0fe61163186236d7ea47580bdbacaf906a55f4825b670701
- this leaf
- 954502c039350c03790384057385dc8d8a4f5c2a1a939f1377b5ad896fb72d04
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- PucVt1IV6DUgEC6UFJ6tCT5lswBoQ8VPrkttt4dsPshA7vkX+5sqjWsrUprdnKLNc+MFDx2nr9FS55X9egRDCQ==