why2 reasons
mandatedestination_not_allowed
op 0 pays GDZSDBMHZAT5Y4WJ65JYHHXZBURXLHJWGG2ZTSUQIFRRKOU4YQWPOF7Q, which is not in the allowlist
counterpartycounterparty_denied
GDZSDBMHZAT5Y4WJ65JYHHXZBURXLHJWGG2ZTSUQIFRRKOU4YQWPOF7Q 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
- 94e998605e342276bdc00ca5b18352d431a4210a367927d0ecc377368b468d00
- request
- 22cead0b4cdc333982c0f29140bb4edebf1d36f48c4febc58b2f9e3458188dcc
- transaction
- 4702fa15463545d08911324953c2552c03f9dba4771abcd23bbfbe5d51fa3036computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 277
the chainentry 277
- sealed to the entry before
- 819c11921e2f3daa5836c0299306132d42784cea5d39cdd6d686e8039afc1b49
- this leaf
- f67ff26713c9c58db58883f9ead38b073105d90dfa7ecda2037f833f425ff30f
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- LLpj9Dnc/ZQzjLGWYwdBUG0QiDmg1RpwcMhBnjqJJbD+q68LjHzHW44f25cNYaO/OnIz7JxB5ORC6jUlNqydAQ==