why2 reasons
mandatedestination_not_allowed
op 0 pays GBXGBIFGOQDJFZ4T4DFJ3QLYH6O37IIQHLENEXB5OJX4K7IX2YRFLRQG, which is not in the allowlist
counterpartycounterparty_denied
GBXGBIFGOQDJFZ4T4DFJ3QLYH6O37IIQHLENEXB5OJX4K7IX2YRFLRQG 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
- 48ef53a39cf0acaa8077fb8bb154460a07a83d2771fcceca1bbd6ca448491207
- request
- b96877d4932c6f36c7c51aeba75d1ba187e0efe70c8f0c95f0ba645e5a4502a6
- transaction
- dda30e72217a0f8621d0175c7a2f7abaf47e25044b1c8eb94d3f0a9968c77a85computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 5208
the chainentry 5208
- sealed to the entry before
- a56ca03840aaf24b94255bbb63ec33576f3423e38f853a3f8b3caeb00c486732
- this leaf
- 9a2257d936e238fdc3585b2e2661c63147674ceed2216cf51e1832190ff1478c
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- lGyhenSB3heXaqbelIXCyMuG4jZBBTZHwZ88p0Ws2lsmOdCiQTJINvLT3NrSGTil/dK/p+PPa8iokVx9TlsJDw==