why2 reasons
mandatedestination_not_allowed
op 0 pays GDXLIEYHSHELH5ON7TLALOWRILXKKSSUAQETH7HZ3KCWUCRBZE4TNY4I, which is not in the allowlist
counterpartycounterparty_denied
GDXLIEYHSHELH5ON7TLALOWRILXKKSSUAQETH7HZ3KCWUCRBZE4TNY4I 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
- 4affc1f7f670fb20ab601bea0e3166e610a0c143d830b18c59ee74589bdff050
- request
- 2c92439fb9e92f3387dc1de3b4c19d2f65ca8ee7574b864ee5245065c563275a
- transaction
- 2b0d50e1af7f7b5d4df45065d9fb29de56e57cff7eb5032f401009b3db063614computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 67736
the chainentry 67736
- sealed to the entry before
- 3822208363642502979056e76e111328e542b1d72491a360fe4ce426f669c2d5
- this leaf
- 5685765f8d1d82906e4bbce7b7b05f637ed22c34e6665b5300d3c58fd1de6b46
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- JOeZRXK4highMSgzv93ktdZp9UWfqzWXTVqL82FO5y0ubHvejaTNBo1JrRu38yrDjE1yUDd3gZCYw1gxUVKnBA==