why2 reasons
mandatedestination_not_allowed
op 0 pays GCMKYMSWRPGTA6363AEYFUPHFH4L2EYK6XGYK6POGL4CUDPEVVHD7WQB, which is not in the allowlist
counterpartycounterparty_denied
GCMKYMSWRPGTA6363AEYFUPHFH4L2EYK6XGYK6POGL4CUDPEVVHD7WQB 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
- e830fec6d6b69f8f876ca04f7c471c30dece92a89e2ad33ea14740309053ac49
- request
- cc88604beae73f5d6c5fb6de0df5f3e73c137220d9768510a22c1676505c34d5
- transaction
- 6e1fb7bd177930a8f14df2ebed28894b7f5541278708ed6d179ecd4215e50580computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 36002
the chainentry 36002
- sealed to the entry before
- f8d42bdeeaae8677a77930924329dd36f1da13af4a7dced674b57d8e5f6b7a16
- this leaf
- 3a9fd383e0fd792f93345a3a576ceacef56cc29b4b5e21a5978184df9cf04be5
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- lZdnXSsJ5cfmluTqxFX1+7iNMf5XZVcAgqQaDyZNrELFCMNX9WqK3XZXumNEtMR7OhYUAcdzHEvwfyqkmveQDQ==