why2 reasons
mandatedestination_not_allowed
op 0 pays GDDKSUVLNNW4N4KPKEZT4UWM6XQNKKHYINTBOM4BJFZH3SMEVQDKCPE6, which is not in the allowlist
counterpartycounterparty_denied
GDDKSUVLNNW4N4KPKEZT4UWM6XQNKKHYINTBOM4BJFZH3SMEVQDKCPE6 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
- b3b4d3f637c52c04ef108a134f249178d2b093bfdb1d45c9ce51dc46d6d0c558
- request
- 1e6742b4863258c4a40068fe5836b37567692ead51c1835ff67fcff56052127f
- transaction
- 14f98c3d28d01d0312edfd88cea27fbe2d9a3779ba85c0a18b3cfcc74d8a5f8acomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 918
the chainentry 918
- sealed to the entry before
- 1da83d80f3b5001d7462ad116b69e7a84f8c6b175174023e16fa1e1ee73b459a
- this leaf
- a970c9c5482d3d54423d5a0605a181d57fea6e3f0e9037d5891a744f78466567
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- czWoVohjbULUw4VLSv0nyEpTcyHDQ+NTs4hojXkv4cg0scjjj/r8fTDl+P9EL2G7jpHaODUWLrOEwWCLI9bHAg==