why2 reasons
mandatedestination_not_allowed
op 0 pays GDSZBZOHGYUULHFPOUYMPVCE5V6DXS7BUGCQOH2K4UKDIGNQP6RRQVBS, which is not in the allowlist
counterpartycounterparty_denied
GDSZBZOHGYUULHFPOUYMPVCE5V6DXS7BUGCQOH2K4UKDIGNQP6RRQVBS 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
- b858a8155ec1143aaa390a841afb68c5b449db189c43817e2b9022a976b3304e
- request
- ca44a64e45046ce54add450bdf3b8b2bc7e0a306871479082d1ab53a094719be
- transaction
- 2f9bf5d01338db3481df5361d22df08f6312128f902429e84258ece2b2c8cd43computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 39435
the chainentry 39435
- sealed to the entry before
- 2ef136d0e202619bad46ee403973cbf7b8ca9df10f8063bacc233fe77ba75c8a
- this leaf
- 589e1f1bab4b6f71955ea5079677c633569ddbbdec6783ff3463240d51a89431
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Wk73LlzYcJ8HsVe6cg0mVhigYVGDLp0+4jR9d2tQfMuxLWC8FXfShKVuJcMQDCh6f2hzj8RTQD16yjoHm54VDw==