why2 reasons
mandatedestination_not_allowed
op 0 pays GDELGKSFYDLHU3N5MHYTA526OFXHJHMJZOOYU6A4GO4PE5KYVPBU7HEB, which is not in the allowlist
counterpartycounterparty_denied
GDELGKSFYDLHU3N5MHYTA526OFXHJHMJZOOYU6A4GO4PE5KYVPBU7HEB 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
- a515df587d4aac3942fe1613e1b4771ff1ce694775520689213c207603bff24f
- request
- bd7033c7ebc766c475f5c8dbd71bf3e4da826fa7267caffe810bedfcd3ff33a8
- transaction
- b93986cbcfc3c88fb0b37355ad014825bf3e2c1f7b15dbc4ba636a7ba37807a3computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 452
the chainentry 452
- sealed to the entry before
- 841b4adf421e288fe6f5acd49682c4fa2f49a18c338d5b6081e500e89c43602a
- this leaf
- d0361f0e5b6239a44df94818ba117e00332fd78e0f31b87a0f4370c10c8cd10e
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- w+WL0BbkrdKgY+N40xKrLwwProv2LLIDlFF5WEsogZpL9DTl1MaHJBj2Pt351ipfFjv8m/hqso698vL4L86yBQ==