why2 reasons
mandatedestination_not_allowed
op 0 pays GDE33V3SLKDE6YJIPM3RIAI2T5IBO2HYJP34DSTVSXAEHHKX24EJPBGD, which is not in the allowlist
counterpartycounterparty_denied
GDE33V3SLKDE6YJIPM3RIAI2T5IBO2HYJP34DSTVSXAEHHKX24EJPBGD 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
- c8df3a0001841c7d18e98a3191a045055bf5a9c9f0e9951ed7817ff9d4a092a7
- request
- 23f77a02c4b7e86403d6b7f96e8003075ee2de6c36f724268c5896de1cc00e56
- transaction
- e6af99adfb4c0383883c481cce7911c565c9c2d91b8638060bc019797c1ea480computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 35717
the chainentry 35717
- sealed to the entry before
- 97cf3881ab777d01ab468395d0ffa7606d1fcc0803e3c9f9b17e2221d5d25b1d
- this leaf
- cc13a510149aee36f8419f1d329084f5503573299148848d329db8eceb245ad6
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- /HMGunvkUWUpQEfJk5rnGP/XDov2cDAExhaDWuAoAhToPt607a8Da8OfyiT4HVXZZhIoTqE2FpFOz05H1D+lBA==