why2 reasons
mandatedestination_not_allowed
op 0 pays GD376QHYEEYY7QODVVW5AFMZ2II4UQQHAJWN62BBCC7L6MNXUQZ5P2ON, which is not in the allowlist
counterpartycounterparty_denied
GD376QHYEEYY7QODVVW5AFMZ2II4UQQHAJWN62BBCC7L6MNXUQZ5P2ON 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
- c5d37767d7b20bde59ce70766d1dbd8ee2f3838b51c461b5738c5e8af6efb718
- request
- 6a8e63b0e383e6a69c0fe7fb7dd5aa9c37050d8802ed209a2fbdfbe17a63f3d9
- transaction
- b4a1712e875d5b9baee32ffe43f2d624c0cf52cb7e41da1c03ae17166d2dd904computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 68866
the chainentry 68866
- sealed to the entry before
- edbf3fd401051c6f2ca0e8827d4cc0f2a4b95bc1b4769b5570faee283c6187d7
- this leaf
- e6afed30df1f503f062755c4d80ed324f85873a7d8f64d6c184b2b5b2ce796ce
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- et9+1xYHvdBMh2Y5NkP1vyzlJtkciz/PoJLeerQoSzfXVRbxChK0QvxGUdNoymgdCvtbA0bFkVuoHahET7tgCw==