why2 reasons
mandatedestination_not_allowed
op 0 pays GBNM3QKKMQF7MQJYJCJ5E7TYEPGKUWNC2OWR3WLVS2RQQXTFJLATHWQB, which is not in the allowlist
counterpartycounterparty_denied
GBNM3QKKMQF7MQJYJCJ5E7TYEPGKUWNC2OWR3WLVS2RQQXTFJLATHWQB 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
- e9067fce228c040cfa5afcf2eddff2a4aa43956314c406bb83b07f0e59a65c0a
- request
- 5f2833a6b86894d9d7ef84cf18e8a83c56bd343d2744f1617fddc6dc46402c73
- transaction
- 84bf0f90ad2d9b4f6f3a29c1e8dfc2827c531fa2f711e868376119700f7adb10computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 48230
the chainentry 48230
- sealed to the entry before
- 3e81b0a53a3a83e28c6f0e16a70a48e67ba0cf4642b8d9a4db91d545675bad96
- this leaf
- d0482ac66f2f843c0aff523be7caed32574d8e0b8ebe625352602f24bf43bd57
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- vfbMADdZIMkLViZoCtK0m5EsnDri0CiyVx5QK68KR8btez94/Dkb/7WM45iZIlrenfIToY2gUYBhJt/1vvqxCw==