why2 reasons
mandatedestination_not_allowed
op 0 pays GCK5AV4F7OAASNOKLDLFMFKXAAAM5QMR6BQUYY3N77VJSL2M3P27CLD3, which is not in the allowlist
counterpartycounterparty_denied
GCK5AV4F7OAASNOKLDLFMFKXAAAM5QMR6BQUYY3N77VJSL2M3P27CLD3 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
- a1f8a0abd005f3d6c0cd8353e61065abfa85b93a0c1f49d1c2a211aa61e8db80
- request
- b5f3132d5422a321af8bbf66c687b865ae530bbb7b6cce34645b8ea5e851c9fc
- transaction
- 1545842f59df6afb3f51a678a4aa38ecc951a3d4e8b34353fe2b72c8459affd2computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 75192
the chainentry 75192
- sealed to the entry before
- c57bafb00fbad5bd6c23a3eaa9d1566f071e1b84bbaca50d52d7ac6c45836ece
- this leaf
- 801334c55f69f6bac357ee7fc6140f482901e5799e3c3145dc13424312709356
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- altU7PGpCdM/WZm5jYowFAOgwbbMUWm3q7TBTbpl4gcFthOtDe3TSp86k5JKhC7quyemIxilY7R4lOuTvyPuBQ==