why2 reasons
mandatedestination_not_allowed
op 0 pays GCNIRTLBNWO4CR2DWVKEAUND3MVPX7Z3HBFN5FGLY4XI4YPJYCA4UWIS, which is not in the allowlist
counterpartycounterparty_denied
GCNIRTLBNWO4CR2DWVKEAUND3MVPX7Z3HBFN5FGLY4XI4YPJYCA4UWIS 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
- 534ae18bb50bfc78e2b68bf45c4c1fa48b76c2bb078fec8c193db0cf6b83b2dc
- request
- 337b008d57ec57782a124016b32812cbfd7d41e52bcc549cddc8ef48d7f5f781
- transaction
- b4e197f6430afc1a052b5ac2698b75baa53035de638deb04de2bc7ff8c87fbaccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 2421
the chainentry 2421
- sealed to the entry before
- 40e3dd569d211543bcfe0bb83adcfb66610971b022092e8f80997fff5422c58a
- this leaf
- 77cf541e1c24ac1dd37c7c1ae6f86cdbd039d0b6622f5fb948484f5166a8bc8d
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- zIdADMf7rrgi648IFIesPhx83HNYPOF81LTAKOl7cRue9EuQYelgnVD7bkmTFAihhSgsYrTd4ip3conAJHZnBg==