why2 reasons
mandatedestination_not_allowed
op 0 pays GBRFNTUH4FMI6HMWVXVKHCE3RPXI2PUOBGIDMNESW2NMEQZXBLUH4P6F, which is not in the allowlist
counterpartycounterparty_denied
GBRFNTUH4FMI6HMWVXVKHCE3RPXI2PUOBGIDMNESW2NMEQZXBLUH4P6F 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
- a73de08b12ffa807e22990062a3dbd5b206616bbd19f9a912e45db1f79a0d38d
- request
- fb0128c06d73ffa7cedb13fb27624f3ff346f99c4f796369db57ce46d0d02397
- transaction
- eec7e3bf7bc1feca1a26f783e2daf5167e9a74190e46f6a832311e13450da1f8computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 342
the chainentry 342
- sealed to the entry before
- 341ea79270f805a50760dfa45c34c91f31b47b65f4c3b3eba6fc5d29e94e9eef
- this leaf
- 48218927f8946c3f007e9620050f3403b07c52a6144380902c6ec7cb05168a2b
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- cC4Dl/dqH0vOPFujBP7TT6B8e8A9naku3r2RRyIbqc8AeZ7SjSoukQGSeHtVIdUYv0mRRMCY4R3ekixmGSa7DA==