why2 reasons
mandatedestination_not_allowed
op 0 pays GD73YEY7PPTR5BND7YAJWZGUXQZG7PX3ZJPQL2YG5Q2LVNXYVDKQEWRW, which is not in the allowlist
counterpartycounterparty_denied
GD73YEY7PPTR5BND7YAJWZGUXQZG7PX3ZJPQL2YG5Q2LVNXYVDKQEWRW 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
- 4ceb8fdbc858fa0f4624736206e377b536a006880bbdc591b6ea0219b06e8a1a
- request
- 7b4696e11dc98ea6dfbcf7987b4c452b21a879fc60a43eb6628a3a451b67fe54
- transaction
- c974c46119a7b515972ce49e5ff843edf2676186f63724735524e187c74f79cfcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 30846
the chainentry 30846
- sealed to the entry before
- 2ddf3d9de15708e17d6b0c2b1d2d3af97a38d0bc254f1658a679cfbc6235c260
- this leaf
- 268cd348908d2f2dc4f646d8304b37c1bdfaec095f38ee4ac845a199a86c6a68
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 6lcdtwz1WZh2DzE3ZDZKuTYXXdfVMtqkAEANmZwRXSbLXbgpOJMAOQiDBrRHGLRMoWFg7RBZTfoQVvyQ6D0nBg==