why2 reasons
mandatedestination_not_allowed
op 0 pays GARWO5F2GDYHCFUYFESTZNLWXAUWWWA6GTL5O6DQYNVWJQXE5MIF24OQ, which is not in the allowlist
counterpartycounterparty_denied
GARWO5F2GDYHCFUYFESTZNLWXAUWWWA6GTL5O6DQYNVWJQXE5MIF24OQ 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
- af042efc12cf14af717800a79482d0a9a3275bd0533b472997dd412bfdbe3bd7
- request
- 864b932fb1567d7168c21877d86c79fcdbe3b07137a4ba6476ad561282b4c5ea
- transaction
- 0f7778914e911c3eef5d53f4de40d1320c8758f109b3af4e5d45daa9f92135d1computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 7639
the chainentry 7639
- sealed to the entry before
- f8fefdd105eeac4c944005b953291011f2567421bce902741b3ba6177fdb6bcf
- this leaf
- b2731022d52a5fbaa567e43896d66a2ca1ccd74a2dca22ad0c49eba2fb3618e3
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- /9+H1RNJtQaLKGWgOx1PAcxxg7NT7eE8w6Uf4rkiX6SqC5NgLnzwz1hGkzo72NZ50Q94loSFUtJgVpfyxhRIBw==