why2 reasons
mandatedestination_not_allowed
op 0 pays GBGQO5XVOAVTULGQS5A6Y6ZWHWTIAXYJSMZNKM3XYCY4QKAE7NFLGVGW, which is not in the allowlist
counterpartycounterparty_denied
GBGQO5XVOAVTULGQS5A6Y6ZWHWTIAXYJSMZNKM3XYCY4QKAE7NFLGVGW 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
- 24af61d77a3c6cac921693b85ca9279f4d6793f62416ba5f645f33b23312be11
- request
- 0abe59c10b51d8f15ca3662230c6463bcb3054676fa12848111600e01d8f90d9
- transaction
- cefeae07366d060ff2059813a16e49797d42bb0e96f5b3e37f30a6f3447f00c5computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 26887
the chainentry 26887
- sealed to the entry before
- a6821e5662012f20299eab879130f8ec40bfce946dfe9b06b1825f5626e4de38
- this leaf
- 6050a13107c0755f063e688b06f0fa77fe4dd7c5c4d23e95459e55afca3a1856
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- ZvKO4V5mCNzAtVPWsDNgeD+FOCdoI3PgssPMv+Fhf9ldcNKesYMfBezzkbPsUL2EX1mUlNsCK5Ui5FeMl9Z1Dw==