why1 reason
spend_windowspend_window_exceeded
this would take GBQM55NLH2M3XW2PBLZPLU3VKXBZDSXRYOCKPFWJU7NJW4SWFRHTRTWW to 30 over the last 60000ms, above the 12 window cap, with 0 already spent
what it was decided fromfingerprints
- rule compiled from it
- a58e3a0f5c7d7af492d60fce2bcefeb95372acdcef7823e3fc8c462903a21c07
- request
- e01feeba1aa3b6ec511565076516cccdd3d70812093abfdb396f0608923c91ed
- transaction
- c3634f5a90751183a1b71eb9ecb136abd0c7b1368120a987df14253d9785bd02computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 14600
the chainentry 14600
- sealed to the entry before
- db47189f388cdf10fff7ade6cf347adcd965c9631583301c6efca46808a720a8
- this leaf
- 646e5ac10b54632381a037e2f8a6619d4216f579bfb4f09afc3a878de7982795
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Kr40pAtXuYE76fZ0S69YLdKmIjZttzS5ifBqXojW7jqtmyvg3rk3gXNgneeLthO1bOuqdOPIb9lZCZHbdlqTDA==