why2 reasons
mandatedestination_not_allowed
op 0 pays GAO2LWSSRUA4AUB35JL4JHJZOX2FZOUVUA7AERUELR3KWKGX2IL4C5TS, which is not in the allowlist
counterpartycounterparty_denied
GAO2LWSSRUA4AUB35JL4JHJZOX2FZOUVUA7AERUELR3KWKGX2IL4C5TS 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
- 79adba7b6160f811c9c0a61f0f1773f7209b80827608bc9fd584b0db7853eef2
- request
- ea61dbb9ca245956eda54cf3b4149b5ff0f3edfb412b1bf74da2899d539208d6
- transaction
- 6039887ba53d7cf2f92de096592ec66802be40a2b9f11f8451f2059760f103b0computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 42070
the chainentry 42070
- sealed to the entry before
- 45537b8fccd567886fcadd8c683580675eef62f1de7da7f10ea517f70f421826
- this leaf
- ea2df33fb9bc669ac910eb915d98f0587ca9077c49fe3952c0d08114e0d94431
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 3FApOWFPatSJ9otRqjlniVvs8EymaPL5IOTA+5H8yCIGbXJHUdlID1e1NBUI+C82YiouUi1KX8t6a4rx4kDmBA==