why1 reason
spend_windowspend_window_exceeded
this would take GDIF33EZYJOQTFPOA2COSMYL3Z7HTDELFJ6K2VDBVSODGQKDDTM65GCQ to 30 over the last 60000ms, above the 12 window cap, with 0 already spent
what it was decided fromfingerprints
- rule compiled from it
- 59fea24c40ea1f160719613d793fb9a6001e29d414eb5a497c5c1ebf355e78c7
- request
- e36e19ca2fbf8abc887d81e011c5e7a4f4313d2325221cf5e38aafbc193bf1ed
- transaction
- db4f42480bd8164153e264d1fe794ef98c96328f01e760db10ecd64c8a4b687ccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 50307
the chainentry 50307
- sealed to the entry before
- ae545ae52b76f5f992a43db67f8226b017fcc5f8adf3e461c038065f9286ead7
- this leaf
- 755de788b260ceb0844aa3091028403bb78f4056454d008cc3bf55793f79ef75
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- dDkqh0ij2o34ivgjPunKx9S0w+lG7kSbIiF5No8+GHW/lgyXew15/ZKdszSN8KP5asIwvohP99kq37+Yr1tBAQ==