why1 reason
spend_windowspend_window_exceeded
this would take GD7XWS55DWKV5UDKEO2HH3P5IHZWTH4D5B6C76M76H3GLTJQMCSNJMO4 to 30 over the last 60000ms, above the 12 window cap, with 0 already spent
what it was decided fromfingerprints
- rule compiled from it
- 4d6a4f392bab47250792476efffb1c119e7cb8d6594db19cf6b25cd674908544
- request
- afc2cb9ef2a7172407e1ab1e26905bf59f812e94340b0c3044e01db033cf0b60
- transaction
- e84efcbadb17d188af811916cd9a096c518ca2cb22a9e10d75e02c8af9057ddecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 26059
the chainentry 26059
- sealed to the entry before
- 91e03abf6608d553cf4de9f4bb1ec055e92960aa0999172cf31e4a0f042d51c2
- this leaf
- 7df182e563ef49cbb746310fbf8b7393cdcec33a96e3e5672812141eb312b9a3
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- eXCPpzTkL6mURyXOC/1yo1bA2dkP3j/SBaAttccyC+Yf+j78I4xQ2E8DBENey4i0dCrfzhfeca8g8nZuC5iXCA==