why2 reasons
mandatedestination_not_allowed
op 0 pays GD2LYT7QEUTKC2AN2KXFOUDFAI45KI76NLK3HE3MXG6CPAOWFYDEGIZ3, which is not in the allowlist
counterpartycounterparty_denied
GD2LYT7QEUTKC2AN2KXFOUDFAI45KI76NLK3HE3MXG6CPAOWFYDEGIZ3 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
- f282cc787061d76ba9fade30d9f8a18aea2c2886b29b1e1814d1b2499b1e05be
- request
- 88085bbcbe892e8c5ec334c91c4d2aa2d6dd2bc5a3c246938e74bcbba876d164
- transaction
- c33c9adfc6881d24ad43181578e201ae960fd35a64ef90ee30f1fe6455356953computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 76064
the chainentry 76064
- sealed to the entry before
- 8b1ccc07457ddb2f252e669f99f728aa5bca2847f4b6d30dae1a135cca9899d2
- this leaf
- 6037bf298f1d925953744aa5374519d22aa1401b4bd274e74cc00faa7b171f7e
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- jw7zO+fMzRtYK2KomIX0gq6St0U9H1D7RZpn+HHa9YpO82K4y3bOc6Wizan2+hOgH8He0m2pSVlOugrGBrjoCw==