why1 reason
spend_windowspend_window_exceeded
this would take GD6HQLD7PEB46ZVJCY75EZSM6GDSZDYTU5JKRQEZBXWFTQE7RDKKTGHG to 30 over the last 60000ms, above the 12 window cap, with 0 already spent
what it was decided fromfingerprints
- rule compiled from it
- 816a37effbf728fb0916c10a7897281f67f9739fcc0209bfe5bc2411ef3a85bd
- request
- 47adb547647e8de2a62166560792fc9bb51f5d6ff5395a6d1034c71528f1d898
- transaction
- dd6c24c03ee00ebe789ad389b81c416b02a84e00971d34ea1dc029e27176a18dcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 72171
the chainentry 72171
- sealed to the entry before
- 80654c2d3da96425fefa5eb576d90ffaabb1a833997172dca311b9f9d7a57c60
- this leaf
- a0174e4e91787f7c23c9a1f53f356d0daac75545dc7b096ed4121b542d8b9893
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 66c34tvlLjvhUmLMNb0ntZnWhW6e0fd0udev8II3/e05eNl6jYfN7NLXs/YiIGdtn+ho0Mb6CxXqN56lhstiCA==