why2 reasons
mandatedestination_not_allowed
op 0 pays GD7EWAIUPY6RZ4TXCAJR3M5DIUYDE4UQM5LWDT2JSQVLKQ35LCKODWYS, which is not in the allowlist
counterpartycounterparty_denied
GD7EWAIUPY6RZ4TXCAJR3M5DIUYDE4UQM5LWDT2JSQVLKQ35LCKODWYS 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
- a53d9bc9f929722f3b8d69db812d0f123c57cd0ebac619f3029ad505a4f32ef2
- request
- 878d85ef2b884d3ae7addfc15e24df2f41928954c6a292c4f26cee03a926f3b2
- transaction
- 9a8e3c49dfebcc007c18b542dd7c35beab3a29647f3098ab84dc893cb0049483computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 76396
the chainentry 76396
- sealed to the entry before
- c9fd32a8185f64f918b1cd595ee462a05a6379f55d4f9faf8932250b38269679
- this leaf
- 23bbac9ac2fe1d3db9cda1a15a843bb56c85f8d8efd9a4d0df014c4942500bd4
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 8YrAEE/9cTV2UgLtidpSYlR85tFkad/Pk9/gX/+PaGGUf3OKlbPZpH0RCsoOIQ4MqhRV22OowkNisnXqRTF3Dw==