why2 reasons
mandatedestination_not_allowed
op 0 pays GDXCB5MJSQ5XETXRRCWG4EYLHHZM2VF5X256675WRPJ673EHU36SF3BG, which is not in the allowlist
counterpartycounterparty_denied
GDXCB5MJSQ5XETXRRCWG4EYLHHZM2VF5X256675WRPJ673EHU36SF3BG 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
- 836d6ee0cae7a674af45c533614fcadb33c3f08a39f5ca7c32a7d878a7e8b19c
- request
- 77d63e9e4efdf031dd74ee66093e40668ac7cca18b49a2907867c23f92904984
- transaction
- 00f890bdde82e6edc775950f84b00300f8a7915112c50377ffee0c7f8ed31a3ccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 44000
the chainentry 44000
- sealed to the entry before
- ffde9a464ccbe2e76a8918bbae13f46a0e3114dfa9380092ba7cfa50a14c3b56
- this leaf
- 78b99ca9ebdda7b2ceef4a87776eb116a7809e1df282ba143e5f2a2614537379
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- tsCvmofGyYM9/4qHJGfOYPS/iPhgD0DSy8zX3n0L/K7r+wu3lQgHtVvsEsSxlUMKYoPZ14lVTDo4vUA039trDg==