why2 reasons
mandatedestination_not_allowed
op 0 pays GDX5CDWLLJDTWLRVLNGKN57I6N5PHGMFZ45753QGLVEE3FG4SH3TK73B, which is not in the allowlist
counterpartycounterparty_denied
GDX5CDWLLJDTWLRVLNGKN57I6N5PHGMFZ45753QGLVEE3FG4SH3TK73B 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
- 2bed4e817d66fbf323a7b1b55b69b008c85c4d4f911d0cacd6b9ce49eb1bb287
- request
- f3f61e83a15befa53d517392b7816e55e4b901824161eae464438fa54b5f2e8e
- transaction
- b8ca5222f73db65e029cbf6e1a69b6dc66830b2ba0455f2114d4b3f9dab46de1computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 60325
the chainentry 60325
- sealed to the entry before
- 9da5f315d72f289e5e461cbcb9831e86c1d9ba2cbbd0c61b73f78e55469e5193
- this leaf
- 37ebc009650ef81bb9feb91214a28cff3d7396f1dcea96fe7f557145ced877f4
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- eZbMjV/oTj/7gfSEdlBTORHC26tKHYzdeUzX+hIjBGdB37+ZXuRMfjRhRvKa6zy8V+HdW/4UEaVaebK+brFEBQ==