why1 reason
spend_windowspend_window_exceeded
this would take GCC4N66IPNK5CNHAYKUCBCZYPFA5PBWZ56HKNIEVSDUHGMSHMHZY6CHZ to 30 over the last 60000ms, above the 12 window cap, with 0 already spent
what it was decided fromfingerprints
- rule compiled from it
- 6d44e676040c88fa2dcaa516292797ab4915104de3ccadedf1fcb1992fded988
- request
- 200a29be834f576ca7e91ea09291b27146fcb72e9ea618c8adeb0eac4f700186
- transaction
- b8a13847f706cd49381af237a28bf5eca2782234565b66819be47cd0e4dc724dcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 3299
the chainentry 3299
- sealed to the entry before
- 8fa09cf3f73889a1de851957ea7bfb59366c0f6fc295e6aa2e2b9702a9451ba6
- this leaf
- 12c17356992f2c641c9b75e55c9dc811555960e1a66a6a75b77145c4393c1d36
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- dmKTivwvu0YlW0T4z08j2Z2zqQ3pzvN4YJf5/iQTpcvkl1uQLy13tTh6FafZZij8bSeH6Pb7vIMhxYOb1P6XAQ==