why2 reasons
mandatedestination_not_allowed
op 0 pays GDRJKW5VGXXRCQGV4RQZOLURQHDWVS3ASKUOSXKRRISQ3NZ5RITCI5AV, which is not in the allowlist
counterpartycounterparty_denied
GDRJKW5VGXXRCQGV4RQZOLURQHDWVS3ASKUOSXKRRISQ3NZ5RITCI5AV 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
- 8a18f0449fc728f740e166eec26c91bc2bbcfd2ce3291ff471e5b0fbd40c36c3
- request
- 029d0c26fe85f979d9105b155102e4a0da4484c8004c0aefd5940f89755ed225
- transaction
- 641c95d0b4c8b3283352d07cf128ff744220749fabe11f20e8075b30745280d6computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 54866
the chainentry 54866
- sealed to the entry before
- a4b39b67093036fcf5b82c5bd35de3e7539b03c80244c1f8c317898be1c0fd17
- this leaf
- 55701742c39df126051c089ef5544b332ab1ca9b30ae72eb1bea3100df33e65f
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 2xqsGDHjYLtqSaYWttGmvsU39v/hSWQ0T6ay59sZkfeLYlAnGDGkY5Kn1U3U2Nd5Dyd/vzGLuPyjdKaKhtiwCg==