why2 reasons
mandatedestination_not_allowed
op 0 pays GA4ZFVOZJNTLXDO2KPOD5YEE3Z7SZG4BLBDZMFFZ2L7SXIDCOKWPI5RR, which is not in the allowlist
counterpartycounterparty_denied
GA4ZFVOZJNTLXDO2KPOD5YEE3Z7SZG4BLBDZMFFZ2L7SXIDCOKWPI5RR 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
- dcd1d2572b13f6769f6db39d2ff4f63f1f07031cf347606b399466f047a585da
- request
- 7fb0b4e4af0a1ac9c515c67cc913424a0331f85f2ee1b07d6825f7ae77d84597
- transaction
- 0e9c3bee5118ec0d58d60abe882e568444cfc57886a33a72a28e6c6486b6c61fcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 69637
the chainentry 69637
- sealed to the entry before
- 1e4f82bfdff176163e09478d8160e9938bcca0795ffe62507feed501451d385c
- this leaf
- aebc80a3124a7b7535a551ea0d4c10903bcde7ee1567c0e8141b357b717151fc
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- gbmDhDhHDxK/Um3Ok77qolUCoGGCGkn5hFW5EF5vHfdUsu+MM2RwIyLeESWkrM8UzrUM3S4lXVXARa/irzqKDg==