why2 reasons
mandatedestination_not_allowed
op 0 pays GDXLBU7E7W7VQ337SZUUS5UXQTITOQBES6BC4VEJKYRI7LLPW6HS7U32, which is not in the allowlist
counterpartycounterparty_denied
GDXLBU7E7W7VQ337SZUUS5UXQTITOQBES6BC4VEJKYRI7LLPW6HS7U32 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
- c3b1a4cff043f289e8ed3f034eba6a613b0afdf665a2d34e0fcace36dc02e036
- request
- 1a2eaf35b4b0bc1c972d4d2c2606e37a5d3996144810849ba01f5da1c13c6196
- transaction
- 0b877a0f1a580a2e6cd7ade521414c05a1e9d3f1dd46f8907d06a4cec89256ebcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 48787
the chainentry 48787
- sealed to the entry before
- dd1c16f6efbce3c0d847221ec69ef559a8a2d849fcab8bc112bf4f6abc344ad7
- this leaf
- 26915307801482b49c3221d8aafa3a0d8fafcf48272cf01544219bceb9f8adee
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 4FkY/B9jnzlGVDW5AnYhsckc7evEt2ObKaNBlPb9shzyoPErn02ywECzaau0WMJ7pL+iJMMZY17jhBUAbDf5Ag==