why1 reason
spend_windowspend_window_exceeded
this would take GB4RST7ZS6CIE7CM72E2JZJCPRXQBFTWDCFZGHSER3A64ATEQZUM5RAC to 30 over the last 60000ms, above the 12 window cap, with 0 already spent
what it was decided fromfingerprints
- rule compiled from it
- a2c17e694174c997f092e1e0a08811a3be0b3975b346a7a77e42b4b17775c3f5
- request
- 142954ab7ce6856d6fdf8cdc301ed1956dd13995ec775bc5807f7aeb532cc096
- transaction
- 94ab7829536ed85c9e5d77ff2207f343077627afea0f1820ad6669352e314c93computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 6000
the chainentry 6000
- sealed to the entry before
- 95472e17ba8ff0a73f87939a14b1bde07fc05cba85fb5e7d32983e02befc4383
- this leaf
- f244e5696c3d4d4a78b85934143369c0992483c92efc0b36484a026e1948224e
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- OQvcIjpLJ0UudLNfQL+0Qb+uIa2A/2ztCRrDcpVET3E1TjeDBWhMBNsrcg5skyEyB58pbBOILYjIhVboirt2Cw==