why2 reasons
mandatedestination_not_allowed
op 0 pays GB5HZG7FMTQHZ65E5YVRVCDKDV7Q5KFFX7H5G6KLDIALZG6M45AFYW4M, which is not in the allowlist
counterpartycounterparty_denied
GB5HZG7FMTQHZ65E5YVRVCDKDV7Q5KFFX7H5G6KLDIALZG6M45AFYW4M 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
- ec6a981a709d312c5fa830557d54ea3d6610909d009f4c32b7a07979fbdf4b0c
- request
- 6373d5ba95b7a1cd8bd08c2e8d7f167a772fa13ce74759abbec25c76c4de2e43
- transaction
- ff4be95eaa38e08e1867fa9961d568b1e3a0d0ee4e29f9aa65e998178322faf7computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 5246
the chainentry 5246
- sealed to the entry before
- 4ac35e8ada32e6e1b565e22c907f8d22060b5b03324677252c081f7aa064cb4c
- this leaf
- 6b119cebabbba35e229672d03673137e04416270417750280c321deb1d0badfd
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 5HpHJVqWZvr4CTwdKfdT6QlwhvgGjiZlKT9Exblx3Sm4QEEX9UyS2aZskkP8YDNAhPRsrYBPU8aU6i4zdUFWAg==