why1 reason
spend_windowspend_window_exceeded
this would take GDKIN4JHGJ6ENSV3TSVDVIDCUXXFQYSBVZLQTQUBFGS25RW2YMR5U2OM to 30 over the last 60000ms, above the 12 window cap, with 0 already spent
what it was decided fromfingerprints
- rule compiled from it
- 8c9e93f1ca74f0bb648418374caad9a7440a982dde221ca526853f5a26697214
- request
- aaf4987fa44da53fc787c6eb5a5fc2da457b144cfd75404f7f20c24cf3354a05
- transaction
- d1384abf01994b86ffcb800d2896e1bd1e56a8e25171f90e45251aaa2b74f03ecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 19515
the chainentry 19515
- sealed to the entry before
- b5f42c4d538349f6169b6328d16f1c43b5d45f503f3edb1eb813512c3d56a380
- this leaf
- ebeb1e5b3d9d8aaac68a679938bc6effedc7253b0201bb60158a3e09902724c6
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- juse3n6xhr8l7pfrYttj0+tCfvPXT2xPmsPqD+kVT5DJLzKJCjT5/UA5iOqlBk5tARXfYJqt2DzC+xah4lrxAg==