why2 reasons
mandatedestination_not_allowed
op 0 pays GD5WSWW4KMJU3G2ASJY2FNKN7F5C6SIR7TPK7CQ7PXEJZQVZ5ESSHGBZ, which is not in the allowlist
counterpartycounterparty_denied
GD5WSWW4KMJU3G2ASJY2FNKN7F5C6SIR7TPK7CQ7PXEJZQVZ5ESSHGBZ 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
- 8854371f0e3e0cf7f413a4b5b9fd4fff5197aa83fe88798ad4a9b813439078fc
- request
- 30eff0080661158ac9007661ba974b7a84a9ed29687ef503a0d06cd4575338c5
- transaction
- 2fae222f036780865532a3da3552c9eeb37b4425a4854f7a48955d107b3ac248computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 27648
the chainentry 27648
- sealed to the entry before
- cfa0c971d5464d8548aaa37dd43114f8e600be5f24ab9d16bc02a296c1fc2cf4
- this leaf
- adf45499e18c78de07b27eba0f855b131225d4a96ccee52877f315db92ba8410
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- w/8OUndWKw5ebfJVl8dBOKRMqOCEs9yFasL1h6LXz5B3p1n81l95I72O7OzU+eFnu2StiMbKkgH/DleDUEi+BA==