why2 reasons
mandatedestination_not_allowed
op 0 pays GDW7L4VRHB5DLGJXS7FLEHQBH6QLSFJKA6HRZZRNYQ2CFUAMQJIHB5YJ, which is not in the allowlist
counterpartycounterparty_denied
GDW7L4VRHB5DLGJXS7FLEHQBH6QLSFJKA6HRZZRNYQ2CFUAMQJIHB5YJ 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
- 872f37a963b15a5abb5ea906f87683b5815b6b4aea81e44dedcc9d101d58b677
- request
- 7c339d7594cdb30883a75bfae84c18aca68b6c32fa4bb2413a5f75947dab2383
- transaction
- 7b04267c41fe5dd5459b950e346280cdbf9f29d96fe95d526c90f12fca82223fcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 72374
the chainentry 72374
- sealed to the entry before
- a5de1b6ce0ef6e9960ced691ff687dad89c4f94a373a96918be5568f77861acb
- this leaf
- 76009c1f5efe03a4f536096ae45aaac3447a3b1c02fd2d5fb19420b05b0d01f8
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- uPUBEOldfUzlMoq2MO9ckI8LnDuIKMsX53h/kmw/Lva4SD8vTYbAO50+pkJGBaJUl5rEhu/dI02klORtKxQxCQ==