why2 reasons
mandatedestination_not_allowed
op 0 pays GDUGE4Z5FJY7XZ254KCYNLBCOMHYJ5RFFDGKDZTY3EV7ANYVG5EKDICM, which is not in the allowlist
counterpartycounterparty_denied
GDUGE4Z5FJY7XZ254KCYNLBCOMHYJ5RFFDGKDZTY3EV7ANYVG5EKDICM 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
- cfb860da397a3c762035af5c863f5ad96b3e6e7cd49d3f182da7ef7675148772
- request
- 480d00439eeda755c4266455fce2e8c1dbbb860abc00ce2350a15b146cdb85ee
- transaction
- 563005453f296814fd143b6e3f96ff371718163aa7152d0e9c1af1c629434555computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 1766
the chainentry 1766
- sealed to the entry before
- 24407d6a02930a139a3ba013310f13167096354420d2f78de04f5352691df865
- this leaf
- 05409b66ba9d2da08e74251179a26f8e960393ab95ab83687ca4c32fd09b8d09
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- WIcM+EdakwZSYW/lazxi2TtFsX5zuUrGP44RoOYhkQPmIAHA78UOKHR8S3empKMNcuiIfEJOu2b8RrfzjbEGBw==