why2 reasons
mandatedestination_not_allowed
op 0 pays GDNFB7HAZWS6SNFL7PIYPLTKB26ZGRCJ3O4SBE66PVCMA6T3RBV5WXJ6, which is not in the allowlist
counterpartycounterparty_denied
GDNFB7HAZWS6SNFL7PIYPLTKB26ZGRCJ3O4SBE66PVCMA6T3RBV5WXJ6 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
- 649d54f77b30158d7527afe79235473dbb2fd9ece2da22c4132258d53c82a703
- request
- 9ecba779f1a9aafe5873f69010038a8944498742e06c6f3021e19d3295d09230
- transaction
- 944dcf79d6163000f5c8bedbebb3df1fe8c8bb933d7fbfe6547f229964db379ccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 627
the chainentry 627
- sealed to the entry before
- b725f53e5075c3c5206cdcde99d3f2cd7d001301d33f8d90b122ddb792adf113
- this leaf
- 926eabcc9253ad98a316e072be771dfc0a90dc81a3d91bdb7f1220ab7f686a61
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- lb2CPfb04gvd/uYRXZy4t8W1ddgipOd+3gIq8Au3s6JGt0Ip2z5Ogq3s4kw7NO4tITB2B/4zesgZwpCmA0O1AA==