why2 reasons
mandatedestination_not_allowed
op 0 pays GD3D7KTH2CZ5YM2AE2WTSMONJH554MQDMUXB4UNDXNE4VOWHCSG5KKMN, which is not in the allowlist
counterpartycounterparty_denied
GD3D7KTH2CZ5YM2AE2WTSMONJH554MQDMUXB4UNDXNE4VOWHCSG5KKMN 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
- f6f2d088432e0200c5f9aa3093cd45cb4023847fdac67c83362540e3896ce9c5
- request
- 1d738363fd28bde726f4d5df08621d3c6a342b8eeee2e1dcdcfe16c8c0940a3c
- transaction
- b3dc3a11e6d21ded14b22022df37167d9cfbc33f0047e1fb6270b700b63d8f69computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 21885
the chainentry 21885
- sealed to the entry before
- e14f8b6912dabfbdf778fb073f728a5dc2bd68f52847c87079314f876569f063
- this leaf
- 31276f8d0bb7a650931d7521f7adeb4afeb9b920b996be67df1d2175d12577cc
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- MQWLUMN5AK6+iFMfs0kC882nc6fTsjegr3EFfrbRSZCxoDMBiw5EnRUBe+YMfzUMwZQKN6ildTlzS4WD6QScAA==