why1 reason
spend_windowspend_window_exceeded
this would take GD27Y276PW5PKTTQ4QYMU2JGSPGDZHDN66EXDEXBHLOA2DOIFMXXU5HX to 30 over the last 60000ms, above the 12 window cap, with 0 already spent
what it was decided fromfingerprints
- rule compiled from it
- 8e2afe6dea8a5cce0c9d3ddae50258c9e9de2ec8fae3a72f111553e98b91fbc4
- request
- 2ae77884425d79ba3b7314219386a2035dbb1ce57f516c4ac20b82656edccbcc
- transaction
- 304155f39f7dc4a8db13c97f22350666868840b25e11ea3ae295b835ab23c9eecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 37483
the chainentry 37483
- sealed to the entry before
- 4b028669c03985e5372f043f9a2218a72c78e0f2373dadc298f530f067d45afa
- this leaf
- af87063f98b78634e0c44c5db89c99022e0e1bf6241e3b1094f44a0621d9087d
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 7xcV5uC2pYxBbC6J9vntG9DJITw7IWcYN6NWPxjvv9gPLXk9sexysB7wzaLWr75zPESBN5h7IozCizFspnUyDw==