why2 reasons
mandatedestination_not_allowed
op 0 pays GB3S4FYIMKRAHERCLP6UWJHJKJA7VUEU2ZBUMKAXA7CLKU5AH4T6EB2J, which is not in the allowlist
counterpartycounterparty_denied
GB3S4FYIMKRAHERCLP6UWJHJKJA7VUEU2ZBUMKAXA7CLKU5AH4T6EB2J 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
- 81f5d5ce1c59f2a18a776cb97732302574a6480a7a4437e09ee3333c8fa2f9b0
- request
- 1cf273cba842fd939316fa813a5d7e2d23ade933a3eee26c2ba5792434854215
- transaction
- 818d87c0d53c23cf0a3f03a4a4dda701dbc59f9b83c9ddcc078106eda50cb57dcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 20432
the chainentry 20432
- sealed to the entry before
- 7953f79a91192317fdb1b7d7d9f3b92393e843351e6e6a872f77d933e381d718
- this leaf
- dbf78379f068965915e74a08bf3844c7efcad847f13143fea2f2fea3ec9d12ad
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- BEyLeiEJxTeJHGJmqSAr5C7IsbxXSXGala+lTIJ8t6LzKJO0rM87bdVYXfsU5Tb0dGKUKFBDzhG2TSPBxvsVBQ==