why2 reasons
mandatedestination_not_allowed
op 0 pays GAWMB5YZ46LFP7KQAIOU2HBQ2Y4CSE6MHS7SE6EACLFZV5H7CJLZI2K3, which is not in the allowlist
counterpartycounterparty_denied
GAWMB5YZ46LFP7KQAIOU2HBQ2Y4CSE6MHS7SE6EACLFZV5H7CJLZI2K3 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
- cb98a3d797d9ef74fda22bcc6b2876505e6e9f2a66e8b32054643c9a0ecbe38c
- request
- e2ef07dad4a65e112ecebce05a5e3be3c3989c745d462b989ebafd26097b0e74
- transaction
- 25f4d56222d0b1db33c4b990e34fd965891e0904fa64190461fb51f3d43b8db3computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 30929
the chainentry 30929
- sealed to the entry before
- c0df942a9f976bdd943f781ae9f61a1e0482d70f3ca1ed950390b36010cb307f
- this leaf
- 0570e1417a57d3d99569182db0b53a9c348e6521fd48fb7f848b3ec0fd46c403
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- AmSbBWjLSlPDSgwSkK9TrLbxvoySiGGcxJA37F0l1JtP7XviqwO9JX96tB7H1jEN3iKC8rIHOemM+eN6VEVnAQ==