why2 reasons
mandatedestination_not_allowed
op 0 pays GD3QMNPM47KQ2QTCLP63AD3DDSQ6NVPPJTF7QYGPEFQPWOU3P5QL2F5L, which is not in the allowlist
counterpartycounterparty_denied
GD3QMNPM47KQ2QTCLP63AD3DDSQ6NVPPJTF7QYGPEFQPWOU3P5QL2F5L 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
- 17335db68d1a909bbdf1f7f7232725da7b02396273ae2a2f2a622a87757fd35d
- request
- 3b7b08b8c98eb8b84eaf904cd6965a185d9c4a953f10a8478832aef9de4a6f66
- transaction
- d7432050b5762dd82e61603f6940b4f53daa9db2372845d76d3678efb9b58711computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 73147
the chainentry 73147
- sealed to the entry before
- 78df1e91f14cab919fe1f5e5a8add01ccae1506bd22736c4a1fac1c698dca57c
- this leaf
- c3b366c0487468216b7cecb90befdd488a39a7550e94dc4df93cb3d48e4e0f75
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- VkRXymYw/aiPXRl29WqZIVL7KjhfQtuxUzIRJ8Y0skn5XROS5JV4+43eor2f5kQ4s1zn6wmvaVa9q88K3220Ag==