why2 reasons
mandatedestination_not_allowed
op 0 pays GB3CVGQJN3X7ULH5I6YDDWJYS5OGTB3T3G2FX3F2ZZWGZDJU4BJ5QA3Z, which is not in the allowlist
counterpartycounterparty_denied
GB3CVGQJN3X7ULH5I6YDDWJYS5OGTB3T3G2FX3F2ZZWGZDJU4BJ5QA3Z 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
- f610bc4f95e89c646279c0b03049fd1ea42d3148d6c54b6b683a80c34adbceed
- request
- 548b50f49212cd1e9db095de84101e4a70654f773fee84b64a8631e492b475cb
- transaction
- 141059629e9011ec40e3ed8176ead33fdf264489b07853e66f2af4d5e4739d0fcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 31387
the chainentry 31387
- sealed to the entry before
- 88837be85733e241230789050b83b234a6b43d1fdb4534b060086a4e11fd9281
- this leaf
- 560825bd4b2012fe965a5be33a6e3245552b3690b6fbfc4e1e583b5ec7f9f7de
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- n6pdsLkLHAzpTrHQKP960kGKoEBUoIkcCNUwRP/85Wj3zn3Be20hpAs9CfSIblRGbYryVwwh1eli153PPZBVBA==