why1 reason
spend_windowspend_window_exceeded
this would take GCZ4JFS4RM3C5IDQ3RXEHMRXTWYZRJNAQAYCELUSQADR3BIBTOFXPL6K to 108 over the last 60000ms, above the 90 window cap, with 78 already spent
what it was decided fromfingerprints
- rule compiled from it
- 42439d34fdb79150d2bf2a739e0924c0faa1fec248c48ec7bd11a9e6ab28cd49
- request
- c3f4aa083a4713b45c66027a81661f61734c430ac85bdcd41bd1c1f9ce9e23f2
- transaction
- 0fac5bc7eb9a0e63cc1aace201518e8fcacf8c6be826b81e11654d37bcb1c375computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 30012
the chainentry 30012
- sealed to the entry before
- 5750f0649eebc1379dff731dd55985957ac6653df858799a86c12d0311198411
- this leaf
- 468fc9be08727e83c37b519a56d25ec6e2302e8944ad93e2e79a7cf3b777c4bc
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- QUctm0QbOJypTsilazQKGzqDb7Rw3C0Adh3fGKoqJuIv3yBDKB/MbsV4pBXS0vulEyF4LQWNMWw9pPYgT52BDQ==