why1 reason
spend_windowspend_window_exceeded
this would take GBKR64LMT2Z36VP7UJZF3INAWL5QNLAOJKG5GYDF2NXWM2MJICSNF2W5 to 108 over the last 60000ms, above the 90 window cap, with 78 already spent
what it was decided fromfingerprints
- rule compiled from it
- 31ed1d86f11a536e4f512c01cb6cb94e1ea3452b360b8756e790dae50d31ed8e
- request
- ad7453865e45b59819e0f3d37f9883cc379be27bd2197aa37c4a55479cea838e
- transaction
- 3d4dc87b62a02722f4daf3bd83660175dda048332248c959e9ca5688b0aba617computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 72643
the chainentry 72643
- sealed to the entry before
- fadd72ca81e7518be76e199a43aee0b86d7f223f6c20b5b4fd59a2e27d8db8ce
- this leaf
- e01cb1e1d01ebe2e051fc94dc7dd100c313f8a2e244c2c12e6105aedcb0f35b5
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- mMe1Yug5TvRE0sjixb/bA8FEkzutz2bPybOhPBuDxLjoKzk2t9zzOI3Udl05nbMpSOW0EUYFiPrzrrwFJDmrAg==