why2 reasons
mandatedestination_not_allowed
op 0 pays GD3CYZEHB6EGGIITP2U3NNIKFEBKVSCYGVRYXXLIA35BIJL37YBZO6ZY, which is not in the allowlist
counterpartycounterparty_denied
GD3CYZEHB6EGGIITP2U3NNIKFEBKVSCYGVRYXXLIA35BIJL37YBZO6ZY 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
- 8ada70b498fc43268bc62392d580676d0aad3bd159c5cdec8a86e33025fe20b4
- request
- 5996f4d7c33c1d35e533b1047a7da08f9ea7f18bce3b3cd99549a3e1c7f4fe6b
- transaction
- 5a4ba3372fc2788e5702cbabf8efb43646e4f4ee28c092568a46c58173b3429fcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 61399
the chainentry 61399
- sealed to the entry before
- 39656e8c607455a2a047126a56fb729339af4ec25d1921441509fe56299e817e
- this leaf
- bbad86c0e92ee3cfd89c07a540e52e42434fd44f16dac7d19abaa6b21f076822
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- mlwaIh8MUN8N8nXGgPbrq0LSRtMGJLrwWDYBh+LUFqH/NIs3jrOcsRa/y6XOZETyiaoyqBuLlNv2zAewJoyIBQ==