why2 reasons
mandatedestination_not_allowed
op 0 pays GDNPQBSKRQP6N2K2EXJXSCDFOGVZL6DKMHOCVYTDO2OPSEYOV7NZSP5B, which is not in the allowlist
counterpartycounterparty_denied
GDNPQBSKRQP6N2K2EXJXSCDFOGVZL6DKMHOCVYTDO2OPSEYOV7NZSP5B 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
- a8b5488a1203c91a19a6efd49b141a5c8a2719cb74b8240c8ed0d4e27cd24d2b
- request
- 45b7b099f28daf03436972277bc101f9d3755cc2be4320792e8cbf8091b1bf78
- transaction
- daa36c6f65b37a42782ea1a15f98cf4b10550b6cb0b2e28e0f2d6a61472490ffcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 26717
the chainentry 26717
- sealed to the entry before
- d6dcfa959ea603ae4a83ae78298111be59d493dc13cc61685d21eb70f4e0f509
- this leaf
- b1bb63b849128562e1fadb6cc78a53af77539e43b785f85f0c40109a25bf674c
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- ABITfRBC6Xk1pghKjx0j7aoLNZku1wmSbkePz4efg6e7kGG4uyczYB2Vkv0DgUhFGg65wF/0ciMU3F9h9cNqCQ==