why2 reasons
mandatedestination_not_allowed
op 0 pays GC5MXVEU3U6PKBKKKZGLAIPGI65BKLVWU3DAQZGUF3JPANXUPEQ5O55K, which is not in the allowlist
counterpartycounterparty_denied
GC5MXVEU3U6PKBKKKZGLAIPGI65BKLVWU3DAQZGUF3JPANXUPEQ5O55K 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
- 3efbbb70d978d2d7608d7852db5dfb781a106794976eaac0332cd59ab9eb0738
- request
- 3a3bad7cff724b4d77755b0e4060780e612249c2501765242b70aa4f83a2ea38
- transaction
- 210f63d6dbbdfca1957a5a55394a8c6326ba6ad51f2ae0f09dc7fab76ed5c4bdcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 8146
the chainentry 8146
- sealed to the entry before
- c851b75cf1bfac4443f8cc51225c674da685bf7a57aaf4ce287eff6cbd57e07f
- this leaf
- 13519e34af1c80c85717deea697c2c2d83e45cf3becfab2ab0dcde14281993f8
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- JKS3eOeORI1MdzHpB1MyWe7WWKBbhNRbE9UW3gzbeKml5bVtCCJa8GqLfixTug/UHT2BFlCMrfujEERuRkB3DQ==