why2 reasons
mandatedestination_not_allowed
op 0 pays GBTZX4EOEKEEGQ7OB26K5N5KAN5TPBJBL4PMZCQDBWJQW6G55G33JJGY, which is not in the allowlist
counterpartycounterparty_denied
GBTZX4EOEKEEGQ7OB26K5N5KAN5TPBJBL4PMZCQDBWJQW6G55G33JJGY 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
- c008f9efac750868c0dba273940c0eabba6965b79ade3e4ede3af9036ed54273
- request
- 06efa3bf54a281321e7970735fa8fc9a707c84c6ff671bc0b1c6c59d40681c01
- transaction
- 8db88f760e4c46760e6065c4a30934e281362de226556a09301bb649befc06e2computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 63221
the chainentry 63221
- sealed to the entry before
- b9c08811be0e8c88ed94927a0370a5df48650bf54f23b272a6693b675c7bd488
- this leaf
- 9a598774482195c41ebda3e493c26b40a6e2befc82112824c8313f5fc147c5da
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- XuVNSUDw7YMfOOQeWpe50c0LCTboqhzKlCzURbkGuRboidv2oiKhcNCE8reoev+qMBwuRijOyRc+mzj2wWngAQ==