why2 reasons
mandatedestination_not_allowed
op 0 pays GD2LVCC4BN6IX22FE5QAIDDA2KAUPMPOZZ4QKLTLWU5LPE5I3JV2U4PM, which is not in the allowlist
counterpartycounterparty_denied
GD2LVCC4BN6IX22FE5QAIDDA2KAUPMPOZZ4QKLTLWU5LPE5I3JV2U4PM 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
- c5c7824a60c5e3b5def09616aa0cad944ca383aacfad05fc81bcb7f8fe44b73a
- request
- 6880ce5a227da95038628ec15bd4de5ba0d13cce3aac9add468c1672059a685b
- transaction
- 3e265c64d82ef2145dc4d19102eebcf761f981755be924fe3ace7397b7015ffdcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 867
the chainentry 867
- sealed to the entry before
- 419918063051a4fd99982e002075a829c2b8e5a7289e81cdb33dc2e6908e813e
- this leaf
- ef942dcac207f3786c3b15068ce44318ea285c60ed4994c8b3290a0560212948
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- iu4vTgQNkKddTlcBRelbt7E2yGJ21B12UsFOr6QGvyQPrHx84pQn+QclOLgB4gm+t3ncvugQXV04pJN1jJjaDg==