why2 reasons
mandatedestination_not_allowed
op 0 pays GD4S7V35XHVHKCB7XZY35XNYRQ5MDCJTC6C6FCLUCBTCLUEKFWEIOO46, which is not in the allowlist
counterpartycounterparty_denied
GD4S7V35XHVHKCB7XZY35XNYRQ5MDCJTC6C6FCLUCBTCLUEKFWEIOO46 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
- aa73dc8c5dc6dcf4f04e4cf0d29161bbeb39fe0e3afd891b9ac3ef6b99411517
- request
- f648af118c349cbd50ca1221024c406aa4b1fd465cb07e3abe0e96fff0266860
- transaction
- 4ed34f053df5e652b313ade6576e68ec88f13a7e515c4380ab8d3ea8d9d307e8computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 48392
the chainentry 48392
- sealed to the entry before
- d679aaf68d8a6cb8d50e9bfd00bb9cbbf6556b18c87f9a2ad5cc2dc922f7caab
- this leaf
- c856a1b225c0801174e13f8f8372117af65594e63ec6947a8c90424258ca7364
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- X6HLjLWSFsnstFRiop/ABrPFUM4T7i1EB9n2ZZoqjXvTtHtmrzzTiZvXWx59juIvTGiIbt4SAJUnB/aWbTLzBw==