why2 reasons
mandatedestination_not_allowed
op 0 pays GBBVSXP3ZYSTPQRFRAWCWS257Q3PYNZ4VZJZYZPPA3QHOS7KGDJSBSOE, which is not in the allowlist
counterpartycounterparty_denied
GBBVSXP3ZYSTPQRFRAWCWS257Q3PYNZ4VZJZYZPPA3QHOS7KGDJSBSOE 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
- fc43f45e37650afef163b55f4ab218b104137a8e0bbc78ebfc35ef894e2ae99a
- request
- acfb6cbb99cd710762c61d3201130292922fd6a799ecec331e642447c66c1aed
- transaction
- 1ecb0424d76218092cc6f87992c01296c0f945ff15ca2b29124c3afa5f7969f5computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 11986
the chainentry 11986
- sealed to the entry before
- a91f01737d2c70797b829b6e2cf0addef40f2b571a9d569d47148818722583ad
- this leaf
- f96646335bd623b3386b1e0dcd9aaafe69bca14f441bc333acd7c1cfd20f9203
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Gl/9DHKf4usUpYJP4aQAgs4loQ3ELTuzbw95MCTr0l/gNa0lz33Q0kkMjSq1WoRwWx660Hs0z2ZUjaAQtwayAw==