why2 reasons
mandatedestination_not_allowed
op 0 pays GDBG2FAYP5TJDMQ3GIZI3LMP2J4CFXJEX47OP3I3RSS72BPIEXKIOZAG, which is not in the allowlist
counterpartycounterparty_denied
GDBG2FAYP5TJDMQ3GIZI3LMP2J4CFXJEX47OP3I3RSS72BPIEXKIOZAG 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
- 53a82923964e2e388ffade00767f7f6ece258fa400fb5176c5d9dfb3c4fbf0de
- request
- 62ce33f12644f82e7e915dc3faccddbc11ec5eab325daad7e116c1ed73e8aa87
- transaction
- 892a246989c9f2bc06623ba7b696b117c21431f0f21f0fa7edb3cd521a8f378dcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 10668
the chainentry 10668
- sealed to the entry before
- 9e63942653d619e6d84037146dc5ddab4074e82b2c531ff1d0749f9ce570fae8
- this leaf
- 3ccddce3a1ab7e7b22004f963eae2d219b2343524320977b7954e80211b9ff0b
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- D46nWYT3r2qEOjriJSk6MQoebaURiS8NQaFE66dqGGD9puXuwxl3tuXuNUCT9yuWBk1EK9HRvrnHyoosSIBKDA==