why2 reasons
mandatedestination_not_allowed
op 0 pays GBB4SWEUH5PDCFJOCDPJWWB2OOUHCDXTGVRZOQNJRNW63GPDATGEGE3P, which is not in the allowlist
counterpartycounterparty_denied
GBB4SWEUH5PDCFJOCDPJWWB2OOUHCDXTGVRZOQNJRNW63GPDATGEGE3P 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
- 44f8a4f34d6113cdad74ef33317d69da18a55846ac5895933bef3baec5114c63
- request
- 35e5c5f43941e5f2204b05c40c359f620c2fde1cdf9d89f75f41a7db47478587
- transaction
- b27b27e687da49ca98086d34bff07a0d8add30145e99749d474e68ecd6990e06computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 40809
the chainentry 40809
- sealed to the entry before
- caac652168edae66289de05d6228c964d7c76620ddba696854d9ee480dc35183
- this leaf
- a9ce0c1a94065bf4ef25e9fdab3ee6a851bca9900f03788697b02c5ffb9a35b9
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- eYEyd5AfmWK4AhbnOecFI74NUEbWHtZHuQc7dtouGyIUNV1MQjqJlAIXSu2p+dEAJXINEbc8UiTsDo7Ed8IQBg==