why2 reasons
mandatedestination_not_allowed
op 0 pays GB5QON5WVFUBY26K6KA3GA5Z6G2YKM6BZ4N6NZQPG2E5JXPOFQ5CFX2L, which is not in the allowlist
counterpartycounterparty_denied
GB5QON5WVFUBY26K6KA3GA5Z6G2YKM6BZ4N6NZQPG2E5JXPOFQ5CFX2L 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
- daa797d7c183d8b04b0b191efa2fea676a7ae3073ba844f1281bc2566ff10e22
- request
- b0968082cf8ab5d750914f3cf4b066a6d193affd5ca24e9b7b2a2f655fc8f939
- transaction
- a67c2ad0dd7cae41392a1f3ddad303674f2b174857887d2eb63b00437adf79d0computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 1501
the chainentry 1501
- sealed to the entry before
- 7af48b39d0b63c3231dbbc8e260e767f2c8495ff246df398c04020b47b0842ab
- this leaf
- c2198af8be60c865d4388c8c2f338f3dbfe9ca382304189c0014b367a4508642
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- DKegflit+1bCCg+Q85ZkpWQd0d5yxqAmD0lmDOfN7lUXlX2USErnsIuk1F9UX2j8VhVYZHtRyLaaAzqmjrwaDg==