why2 reasons
mandatedestination_not_allowed
op 0 pays GDR5FU7S4FTDG65K6UB5LAIMTBRWLHWMIBH6PTEMPJLUCYN74SCAN5XX, which is not in the allowlist
counterpartycounterparty_denied
GDR5FU7S4FTDG65K6UB5LAIMTBRWLHWMIBH6PTEMPJLUCYN74SCAN5XX 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
- 50bb7b164cf22c6d3bc0337e5a4ad6907e095a5ab9cb0f1e064e2a5ddb65ab4b
- request
- d907cafdec1a1f06ff2e0cbb68a32c30f1008c2419b05d59da99e3c9dbdc4b15
- transaction
- e512c77b655f8027627ab34a1abf8eafd1924ae14f3ffd3a2f38d92221ce971fcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 3023
the chainentry 3023
- sealed to the entry before
- 841e2ed32a91f92815ea6923429950699d024db940aada796a5039a1ebef19b5
- this leaf
- f5a25bed5b430bada854b9e3dde2687533e65282484df297521a5c939eb65916
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- jiAJfIEyRwSZW46vmckQZVCUvjdRpOrVzBRJcMazQPoCUhuhN4OxGuYcGOzAiG/pVdK9uiKaToRjnRaYpcmUDg==