why2 reasons
mandatedestination_not_allowed
op 0 pays GDCD4HYZZ6R2GWSNH26O4S356RU2IZYYXCHN3HT5TRZCL43QRR5HLQCX, which is not in the allowlist
counterpartycounterparty_denied
GDCD4HYZZ6R2GWSNH26O4S356RU2IZYYXCHN3HT5TRZCL43QRR5HLQCX 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
- 3f5b0b38de6f3cd6f72f938ab9d2b955ca4a317e129cbb6aa37533ffc8d2fd7d
- request
- 5d6a42aa322d5ccc29aeeee5e6b31384cfd6a330a66c3e675b7edccd23525858
- transaction
- 3ef29dca2947d27f34448d6b3a13f98feb7254d31a65663fe175abc3ba2bd767computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 68234
the chainentry 68234
- sealed to the entry before
- d53ea62dced769109ebfadd4db3135a7e5b863638b8021654b6347d44471de5f
- this leaf
- 4a4ade661eb7e8870afa2ce512a2d5717ed24ce9732de495fbdc360eb74f79a9
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- /PBWKo1UOk1pW8bZLKNWCp7rBcdfxQIRQtFfbwuUyyw3yvHi6FWOx1Hg9GPVLdwQ3upMkSqiKZy5H3wRJcmsAw==