why2 reasons
mandatedestination_not_allowed
op 0 pays GAGVCSLHDUSE4CQWTGCT2WV4WR5FIVFUOLDQ5WXB3FY7LVG4QW57W5DK, which is not in the allowlist
counterpartycounterparty_denied
GAGVCSLHDUSE4CQWTGCT2WV4WR5FIVFUOLDQ5WXB3FY7LVG4QW57W5DK 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
- 840834e24d3fba16e80c7092ab6acd4a80e4badc0dc400975844bf0981ca76bc
- request
- 5bcbd8797053e94fce4106046c332433ca42e51a9113715c2bef338987fde61e
- transaction
- fa88782d650bad56997a1f5722c8519c178d6e8e78502b58009c04ba95726a3ecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 22987
the chainentry 22987
- sealed to the entry before
- 55fb6565438fecb43927cf2e1df49f0bf3e45b9ff1ba25d499c1ae16f1a82e56
- this leaf
- f2a5578622e5577ceced32a9ac290d28d08681707bfbf290a56050e20e6c09b7
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- zVKzrsJotLM+KVOPFOkvWG6kbaRw77KLdoa3SISBIToaMVVb2J/whU5WCHkmDhFFKC1AGiF7gwxGMmw66GuBAg==