why2 reasons
mandatedestination_not_allowed
op 0 pays GADXMNOORZ3RQHLHMQ6LEPJQFVCQRX2NF7FXI57KJKZAGLGF7AEY4ZGU, which is not in the allowlist
counterpartycounterparty_denied
GADXMNOORZ3RQHLHMQ6LEPJQFVCQRX2NF7FXI57KJKZAGLGF7AEY4ZGU 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
- 87979bb97701cd8d55ec8e9e39dd49572912be96c54cb61c922f48be318c2105
- request
- 2c65709268ca4c871e85196f3bdbda7289e32b338e121c11f8ab5883b26367cc
- transaction
- 8121b778a7177333348c1c92b277c638766eb22ca80a8de03f1f4ab741652506computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 17582
the chainentry 17582
- sealed to the entry before
- 0c2bda0f815fd06a1e48d85bde68ffc94657c87853530b11f2009c9f370f220d
- this leaf
- 9e5e486b52347db25c465fed8086eb82661eb8a946ec54fa562890b30655b79f
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- iIL09jGeBYVzOMlLz4LvgpHfTEVHqnXrvQYW9FhQ4d1w+UH4FCsqN/3BC4nY0oeWmCzm9LW+5JRePBrsHEToAg==