why2 reasons
mandatedestination_not_allowed
op 0 pays GBB5YYUFGZVQNAN5YMGUCONAZKZO7YVKIWGGGE3QFI6W3O6OAYUF6L3R, which is not in the allowlist
counterpartycounterparty_denied
GBB5YYUFGZVQNAN5YMGUCONAZKZO7YVKIWGGGE3QFI6W3O6OAYUF6L3R 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
- 82fbe21a4b020cba88a82d25554e1450aabc1956c7198bb18f8f4949dd3ca826
- request
- 18a615b271de34a476ea0295f438211d818f81da51127471c0e9c9bd2f473c77
- transaction
- 0fe2b56dea568c4d826e519ddb15d2d198cf67a7291c81b1c01a7b20e58c201bcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 72487
the chainentry 72487
- sealed to the entry before
- 272101894a1dfb14823802a229df764bc74cd8a1f631a076136b593eb8b604c4
- this leaf
- a3448ca922451c0125b93454a26fb0b09c7e161ebfbb6080cdaa5cf8d532de6f
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- bCiAbMY31poIg4AesAi38pI9OJYYIn61ipKBzI3tqcWGNBNddVNXu9ljGSSQ/JhnXAnsmgCfXeVT3e1WwUfDDA==