why2 reasons
mandatedestination_not_allowed
op 0 pays GBLDOF3YENVJ5UZU7LWYLLLZY3SGHPFSMXOWZKS5IRFH5D223QYKIHAE, which is not in the allowlist
counterpartycounterparty_denied
GBLDOF3YENVJ5UZU7LWYLLLZY3SGHPFSMXOWZKS5IRFH5D223QYKIHAE 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
- 7d6f9d0a4d669ddf1fcd4d106b21ab387e5f4054993cdc7dfd505bb9d721c957
- request
- 2c38aa072a67465e843522ced479c08908284cdc8de6459fca4186de47555916
- transaction
- 42e5ecfdfb835f1838a521988f05688e0d4112fc3e6dfc7cac181b9745b01cd0computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 44458
the chainentry 44458
- sealed to the entry before
- 31869aefde814fa6036c77ccfa971b84484494db7d0d503ddafe4423419417f0
- this leaf
- 93b54103c7d14a689664e0a2f09d2a37fe0019c687616fe5ca8d70c909fcac3d
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- QYThA3o8ofze0dHnAfCCuDf2MSwfno3MGp+k/IRHVtu4mGTJgnEI8Mnm2QFIWkZAsgytiGsU7qj/TvzqW5dPBw==