why1 reason
spend_windowspend_window_exceeded
this would take GD4XUE43ZI4QI765VFY4QYCVZCLMITKSYCXMVSNSG7QDEZ25E7YM7CRQ to 30 over the last 60000ms, above the 12 window cap, with 0 already spent
what it was decided fromfingerprints
- rule compiled from it
- 9e826c09f96d52a94ad4cc6d43850c4367efb35bf7badf08a93669531bfa0811
- request
- 6febcdcb351fc55b6eb2cd60c7219a7085cf99ab7bad2d944f310f3756c4a0e8
- transaction
- 4bb39431451e2c37682c1184edf1676ec1b9bf3d9a740c0a0fd3ec2e3b80e2dfcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 19875
the chainentry 19875
- sealed to the entry before
- 185c641a1fb8b790f69c8ad405a985be23b7ce412c72eada39f4641f449d3f53
- this leaf
- b7f42378e54b97ac1c49b049ced302e3edda789450e2da480bed309e2d5370a9
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 3i9C3SCfpUpy42Jf5Z7wiiRduXgrWzyojpMn1vXqXeyewji8q9JrGRdb1PGqX7hvXHB6CppR4lP4kQRChypXCQ==