why1 reason
spend_windowspend_window_exceeded
this would take GDX5PHJ2QISC4EIGXV7BD5AUZ7NIPBB2EN3WY6CQNPIGP45EFCB3P7SK to 108 over the last 60000ms, above the 90 window cap, with 78 already spent
what it was decided fromfingerprints
- rule compiled from it
- 8f7d559fd762a46d135b17ba9ab1c0bc6bbef7025b4de0a88d76965e441e25e1
- request
- b838751b309c8e9101f29dfabc0cd25493cebef74bfb6341496309049ef3df13
- transaction
- 2c3df51fa5a985e3cd987e916967abd7c7170155390dd9cc949062edcd181302computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 75013
the chainentry 75013
- sealed to the entry before
- dccc904f11bd63456fb119aa5496a7023203677af72c083450cc769215b332d1
- this leaf
- aa3b8a3166fc545a9e378ed2dcb4fd8e2811d1d269f22a12e795847bc1914f34
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- e3EmvjUUAx4OJXY5bhD70J/wDRzq7dEqGpY8a1dAeWCXsoYq0q08xM4aAE2fTTk/MM9U8n1AufEH3Yfe7VmbDQ==