why2 reasons
mandatedestination_not_allowed
op 0 pays GDEMZTHUKYQRL47XJXYEI4F5EUI2PQXNQ45IBGWDKNDUQVLPD2FBHSJA, which is not in the allowlist
counterpartycounterparty_denied
GDEMZTHUKYQRL47XJXYEI4F5EUI2PQXNQ45IBGWDKNDUQVLPD2FBHSJA 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
- 77d8b2994f761180ce826e38b62a217c58e6ae30f201c202691669aba883fa60
- request
- da7fdca74dff787a17b2cced8565988ce2391001d6e4a2bdb796f74a2330aea0
- transaction
- e6360bafc93fd28542cecf80ba024768086b2bbcc96bb90a43cf29fb99fca4f5computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 53878
the chainentry 53878
- sealed to the entry before
- 9bf07fb69cf35a54c9742cd5e1f03f78c81501e0c803af559aac687e3ac14197
- this leaf
- 9a4a879042e9486184571c0ccb952a03e37c29ecb75b024b18df4428090c6257
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 6hbkBRP49OsQlqrd78dE7KlJgvGcIh3bF4r1WJ1jhN6naSz95eajXPF/Zn3HgFSz0CBf01cNa8t24MRD2fggAw==