why2 reasons
mandatedestination_not_allowed
op 0 pays GAYLJXFDXK76LFFXA7XU573CQ3XU6TFPHOYYK54K2ZKGHNSLAJ5PLTPS, which is not in the allowlist
counterpartycounterparty_denied
GAYLJXFDXK76LFFXA7XU573CQ3XU6TFPHOYYK54K2ZKGHNSLAJ5PLTPS 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
- e07f365b7cd126406e45c2c56149e3a1ebd4993248497499dbb550757061b5f8
- request
- d5170d3055c36e187e3dfc7776f5fccb0d6c8b18e70244a2045c01a97de3581f
- transaction
- b625daf8cbff22b255a057100a26f476c5e4f7a34be990ff26585257592c7de6computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 43352
the chainentry 43352
- sealed to the entry before
- a170ed650193d16dc83941f9b513a6c14c5c5a3265a90aa69da5d691c7dba665
- this leaf
- 6fb3fc68750aaa7e375ba51d5ca61d663e4e4475f67f88dd7df8902ed12d1f8c
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- eeqHwA9UvjsqDBKa3MWdGEaX4jZpRHvXh4kPOU4z9yv2/OgSO4QPkq6GlgrfBSPoUmem40x11x3brT8nTRMqAg==