why2 reasons
mandatedestination_not_allowed
op 0 pays GDA6H3CE7EBJG5EM2FT5T7J6RYKN7JHNKHNU2UCL3LG6JSBLLFRBSKT5, which is not in the allowlist
counterpartycounterparty_denied
GDA6H3CE7EBJG5EM2FT5T7J6RYKN7JHNKHNU2UCL3LG6JSBLLFRBSKT5 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
- 6da41a84b325dcde002d1cdf54947f6c27c716847aa54c86d1709feea24b5b34
- request
- cdd5adfca8b4b85e91663bbfbb5f210ff9dc4fdaf7ba69b098086b6806129d57
- transaction
- 2a5d514cd5336e788b75dbad4fa69f1b77c2994c47e41f8e93148b0e92873d99computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 50542
the chainentry 50542
- sealed to the entry before
- f653f84be14893c67b07925425bc15a7ad9e11e43db2fee39c559cfc2ad6eb02
- this leaf
- 377b5be348759bd07a54c653af74a6bbdf373ce9131d0e896421a12c84e11091
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- xD4mCWH0lLR1LieSQm0IJ39xtJN40QbMv37FqU7n/PkQLGKnb5cLyZtmqtKDn0Tpwmf1VcP+otTIsFoPpHCcAQ==