why2 reasons
mandatedestination_not_allowed
op 0 pays GB4FFK5UMC72EQDHCUPGWV54GZRZN5R44L3DNCYNDLRK4OUXAPQ66U7G, which is not in the allowlist
counterpartycounterparty_denied
GB4FFK5UMC72EQDHCUPGWV54GZRZN5R44L3DNCYNDLRK4OUXAPQ66U7G 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
- 1d8caf3cd5768362ed1f8b2393bce1e28b9282268951496fcbfb612368612fef
- request
- d9dc8c7682b3a94039e36c7fe8aa094a744dd94158bc185a01c8ec0e304ba2d9
- transaction
- ea3e1429c151c461285ec571e4c08b7423701487c69bb1dbb9a6f5afc4b2e8dacomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 40916
the chainentry 40916
- sealed to the entry before
- 34ce3fcceeb18137dc3f0637eef20ea527162d9642fb2d507ce88bb73165714c
- this leaf
- 4982df6f3305ba7ed5a1bdc461323a42d864b8e54d1ff6931606d4d4f9dd5ebb
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- lrBLie9svYW9wBivFjeeyCn8aKs45BFgVUxS/TxfCIEkvubaDGPH2emfwMLAO50RryilKycEHCWser081s1hBg==