why2 reasons
mandatedestination_not_allowed
op 0 pays GDFWE2Z3HCBRXWF62LSSAKGQSHKISRQFKL6WHI4ZUM32H3QL3WH3QPQJ, which is not in the allowlist
counterpartycounterparty_denied
GDFWE2Z3HCBRXWF62LSSAKGQSHKISRQFKL6WHI4ZUM32H3QL3WH3QPQJ 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
- c07aeae128cfef5106b99f3dddbb2e072647155b820c74277812fb8f8adb779e
- request
- 90cb1da3ffba8775ae0e71516c2dda7e5ff1b7a183f84cf35f10f921e1fcb392
- transaction
- ea5e8dfafb527a93b714a940ae0df2ce580b3e23ed51a4045e47d7d444972a3acomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 2621
the chainentry 2621
- sealed to the entry before
- 84677e542b4633352718fed263a336662ffa837a862d0fc6d696eb6e2a75cf72
- this leaf
- 8c6fb30a6d11e08bb04329d079a9c5dbf5aa7309c5ccd04460608180d939c528
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- w1R8TjYwvCJcVWIJA4oGyrdwgt+DfdITRM6kna11GObZd8uuEFhaCFOnX52XFva8ijKS1/GTx58BldkFASyJAw==