why2 reasons
mandatedestination_not_allowed
op 0 pays GDBOF7RT5RX3EFPH36W2V4KQTECT7OOPY5JAVVHZVLCB6QXASNMDQ7Q4, which is not in the allowlist
counterpartycounterparty_denied
GDBOF7RT5RX3EFPH36W2V4KQTECT7OOPY5JAVVHZVLCB6QXASNMDQ7Q4 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
- 90a663e8a83c63e64beebc86d4268fd305de8ff3d5ac229b46fab503515f2db1
- request
- fb77d75450d6e9c24b8ef5a6b09ff7855bf704890e02740c7c2716ee320bc013
- transaction
- c4d9da6eda6ed9b9154d3419d1a5b7d3d2935928b09935adb168ed8fc2b81e39computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 60352
the chainentry 60352
- sealed to the entry before
- e41bf00d843bd8f24eb08b53717e939ce517b19ecae3951b3aed1ebbbe5af2c3
- this leaf
- c4f4e40fd2cd7c0e8dbbcd928d0cc380b09d58be880ee93e55214a7c7cd65e37
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- QsADJr+O4ujygget8v2EdlPaREI4zN8tkBUaw3Zj3ERaRwfIstd60N0PqYs8VtCv0enlGLCIdaOsI5D5bhOUBA==