why2 reasons
mandatedestination_not_allowed
op 0 pays GDUTKTSEVJ5GBF2SQHVUMZNQFRMJ6W67XG4WQCIZKZ6MYEBUHMJ7623M, which is not in the allowlist
counterpartycounterparty_denied
GDUTKTSEVJ5GBF2SQHVUMZNQFRMJ6W67XG4WQCIZKZ6MYEBUHMJ7623M 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
- f1499f2a3e36d25d25ddebe6ee862cb9a4015c8527d69d2d6b00f36b06f02bda
- request
- 7696d428f1b382e0b84e917ba16bc5520069e639e200f860a57b9e48adb8ea03
- transaction
- 00fd4478daa5e607838bacd2dde01af77102f10db894db5bbcc4d303c0a5cc77computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 35259
the chainentry 35259
- sealed to the entry before
- f26c055b5775c600381874022b6201e0266ac91b664b084059ec36d4f3ca6392
- this leaf
- f5190af43cc75719e17e102b2117dfa25b78bb439b5731b0d55451405323e4cb
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- U7Dtwxxms7IG/CosVwU7YYkgmYf0CcaLotryr3MRDyx3UTuexUpj9zb7i0LSlIRI8bgC7Zptttg7HqZURFqCBg==