why1 reason
spend_windowspend_window_exceeded
this would take GDKVOM6LHBXW54C2FYFLFOQIHWFWTEQPMR5TTZMG6XZZPUUEEZEI2MGM to 30 over the last 60000ms, above the 12 window cap, with 0 already spent
what it was decided fromfingerprints
- rule compiled from it
- b2ead1a2d100298e6710fd5ca0eca875f445b49b7a74fbe09a468de5d9fa1d7f
- request
- 8ee2bd506c15d164d8e6edcffda76f6fb350627877cb0c8f6fe91caab0b428c6
- transaction
- c29c966ce9c91066f7673a30d406de724b4daf4e5fa5634977551b43f496a2fdcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 18306
the chainentry 18306
- sealed to the entry before
- 8d8333736a132b11a5aa76b5978325730cbf0131689e817f31bb068c4f7c5da0
- this leaf
- 3acbf028493e6ce982553139e3a573bdbd17e7b5f17bdaf8fd3523906fd6f832
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- wLi57hVTX7lCtG4qlL8QoDU6K4ArXBMrxaoLAGfcdojnf0zbrfeegWrW26DNZAytxHcUiNTY759aCzVjH1QdAg==