why2 reasons
mandatedestination_not_allowed
op 0 pays GDUOL5BIHY7ZQKTVR4OJJW5LNFCQSZ5VIZEBBPG7PGDWIAYE7H7TZT3M, which is not in the allowlist
counterpartycounterparty_denied
GDUOL5BIHY7ZQKTVR4OJJW5LNFCQSZ5VIZEBBPG7PGDWIAYE7H7TZT3M 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
- 821fd0181eb80efaf8652548c75f48211d1caf51abdc12cadec1cba4075e5112
- request
- 05ce23165100d297fcf1da481d1191ee8b416de3e414d6042f644eb3207db5c7
- transaction
- 1d97ce27144b303dd4d7a2c87868db920e2cefbfcd9851c9d068ccae7336edabcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 52270
the chainentry 52270
- sealed to the entry before
- 1ccd81ccafd9898676c99854c9e1f43b82a37fd7b7860ca8610be9e9de59aec3
- this leaf
- fa16edcae307cad7ba071d4c7164169f3cb94300b10169abbf32e0b5d4187a34
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 8gFwYMbgoHu3YUdylyO1Lyp7Ak2wYNfdNAkgbs7Od1DtpT0FqQ8J9BlZJJAEIYth+8x6h+xoe5kUPQNNeL6rBQ==