why2 reasons
mandatedestination_not_allowed
op 0 pays GCP2XPZ3PEHSM5KU6D5FKWH5PAERPFEZJRNCPBVUIVJL7NEX5KZV5KQZ, which is not in the allowlist
counterpartycounterparty_denied
GCP2XPZ3PEHSM5KU6D5FKWH5PAERPFEZJRNCPBVUIVJL7NEX5KZV5KQZ 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
- 214fe2c7a578a2e9e7c543bcedd201357f4284936277a61b9167c10216530264
- request
- 3a286d55bb817220e3f729ec93d69faab298695d29eefffdf4a612b521067067
- transaction
- 9f1e089ce4a6d3100f05c3e2b20e34503563153c0896c89f39a0e8e0cde6627ecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 402
the chainentry 402
- sealed to the entry before
- 818bf888c52e8e368794d752f7358f7562920df3fb46d6571e38d9580844fee2
- this leaf
- 8dfe96fddcd284696205edf1ca3861105ed9cfe66b6fdadbb4732626e2a7830f
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- B5zWZlEUG9cl5dcgB/oF5/rZ+Tk2J3h70U2sgPUzN6Qfm8K9hTXH4ZknSFAQOiigqzdfUT3EHQj295L3HphaCQ==