why2 reasons
mandatedestination_not_allowed
op 0 pays GAKLYDXQ4QFQEVVDGGX65ONQX22A2VKLTZ6CTC6PQMQ2FDNXY7C5MIPD, which is not in the allowlist
counterpartycounterparty_denied
GAKLYDXQ4QFQEVVDGGX65ONQX22A2VKLTZ6CTC6PQMQ2FDNXY7C5MIPD 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
- 0de930ec1d12ae09e17b07ab0769d16b41fac02531c50f114be9ef430218a330
- request
- 82590a24eb4823291d9715e70f4105f337331dd4b8ec4a19863e7373370b6ccf
- transaction
- 496e45edca10f879dec379c2aad7361ff22c5775ab357075d1d92e59512bef24computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 66003
the chainentry 66003
- sealed to the entry before
- e0bd08e36c0aa6ffafd92421fb38bc4ff313ee908615283c6c8e2ab7f6a93c5d
- this leaf
- 2bf845332931ad978042bce38f80ecb18713837c8154d4b7feda0433d7125227
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- pmoMaEZqC1QZhpNaoivh2v560T7hCwdhOq5QxjtNbgUab73YQ7DvnCsTl+PRvku4egn4fhOvC3qGln2WO8bBBg==