why2 reasons
mandatedestination_not_allowed
op 0 pays GD56O7GV6DBXIWCQQFGXRQ5IB6NA44MJL7DYYAK65IWLG5AFQW5DM2WG, which is not in the allowlist
counterpartycounterparty_denied
GD56O7GV6DBXIWCQQFGXRQ5IB6NA44MJL7DYYAK65IWLG5AFQW5DM2WG 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
- 5fe54ddf190d74ac5fcf203241e1c8cb61febc86cbf9c3ebb291d0de71052842
- request
- ff7de6f7c87bdf46fa3052481bf775b67f0dc3cb7c6aa942e6762f7f66a5775c
- transaction
- c032db550604bc515549c11528b500fdce759a43071cd27304d1f2e56221c858computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 52568
the chainentry 52568
- sealed to the entry before
- 651ac0714967c5d8690cfa7a13df56c981071ae8193ffc81605c50c4f4ccc463
- this leaf
- 02a7ef2b106e0c01e23af7b09ed36fd048fbd1c12187282a34346ba21aba5182
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- y62vE+BNX940M6hL70KPbal172/Njxix+hQ7Rw2BTI+A15t2eHoQ5bqQ1TIVJxfZnSe6n/PRCmqFbwLicejICg==