why2 reasons
mandatedestination_not_allowed
op 0 pays GBLHUDPBQNJXK2CJ7AS6JMWBB5NZ2CT7EUW3S6OPFS46NPBZRWALWX7Q, which is not in the allowlist
counterpartycounterparty_denied
GBLHUDPBQNJXK2CJ7AS6JMWBB5NZ2CT7EUW3S6OPFS46NPBZRWALWX7Q 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
- b080ee75a16c4832148475a19471ac7e680ce9b5b6b13ca6758114c6cb2d4d44
- request
- 784f88c8837e98da521ebe21727f9155e2c22f9b6c5e71fd8eba691d62d6ff85
- transaction
- dfe58333e347a1bf44924fec1edc1f9fd37949daf1132c1c126b52d03d1bea13computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 47674
the chainentry 47674
- sealed to the entry before
- ce2ee88ab2c9064d7dbd34f6b9956517e097a559eb6951a048269ff9ceb874c6
- this leaf
- 74bc8282c5da13c8f7373fb2590ff18c2db54410033185f643b42f1ea6cdd68b
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 8ghbc2X/9+wZs3oKoO7+pehIJf35ftRhdtN87qDt45h2DjggG1iKndiycz7r74DaZtt22K2hEnaLxdubq0RDDw==