why2 reasons
mandatedestination_not_allowed
op 0 pays GD4AVO3BM5573OZKIGQ6OHGEZ5DXUZCQYFPDC3YP7SAHQA5YFAAJXWXT, which is not in the allowlist
counterpartycounterparty_denied
GD4AVO3BM5573OZKIGQ6OHGEZ5DXUZCQYFPDC3YP7SAHQA5YFAAJXWXT 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
- 6b0c6c455aeba27c19f8771f5929a84a8c1749a3d358e5540913fb26bd4b0626
- request
- ca705b8e0c9748b27d84a45f706d96a3f5a566ae136b9efc6f610831402999d5
- transaction
- 1f5dffdca144b091d72be5844996f8220953c4c3dfd62a88ba5c6fce696569c7computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 522
the chainentry 522
- sealed to the entry before
- 9e40376f75d6689abcfee1407c08a296abb49403cd7f3461b1b8990049839e3a
- this leaf
- 2a004e1ec8c34088c4a8c0d560462d13c8e3ddc06c5c31a361d77e40ae3b39f6
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 8oDNnMLpuO8MY/pvAM6NEtiBZ2//JVkSjVF5OJzX2OacZyWdRSbKUKpDgOMirHPl2+k1yfXW+ulQqYyvSoWvDw==