why2 reasons
mandatedestination_not_allowed
op 0 pays GDC6LP33GHA4E3QUPLUZDRD2QPSJ4UDZUGYNYZUGE7TXG5GKGVOYUZB2, which is not in the allowlist
counterpartycounterparty_denied
GDC6LP33GHA4E3QUPLUZDRD2QPSJ4UDZUGYNYZUGE7TXG5GKGVOYUZB2 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
- c2508c1fa53ffe8de1847e4302e6dc5a29dcd47904d07d12c2ba1fe56a5e6d30
- request
- 65e1f08262da8d53864ecf108e83041b650342c468e1bc06ab56a0b20844c4a3
- transaction
- 1a6860aee07cea9e0daafd01becf87f0a1cdcfe2c8ae00838592e1c616a4160bcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 10408
the chainentry 10408
- sealed to the entry before
- c5c93f880d1a12603f7b14919f91b23ced4b48819c6dbe02f467200afdcff393
- this leaf
- 317db66cb4a57210dd51e8f954d919daebb73e4a83ff4c1c0b35b9fa4e4c05db
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- BwpzG4wDU1gQi/UnCYYJ4ho3NmqTUj/G77P5V1e+bTE54nmOfAxLHzXEDbU5oo5wyUv+smguYiVZyXPRdan/BQ==