why1 reason
spend_windowspend_window_exceeded
this would take GAZXSHVVUMMUY24UZUBS2AMZF625DQ3OGAPFUJMJMNWWZGSIVGU4D6MR to 30 over the last 60000ms, above the 12 window cap, with 0 already spent
what it was decided fromfingerprints
- rule compiled from it
- 578f1d56ff7bd46280946db78e2c1c773a72ab85239bfeab6e446ad5ff917351
- request
- 467d07cf09d829a046c3a4f71178e5b8b75804cf3255004be685f88ff6994bf1
- transaction
- f0f3341e354358ca8f38856abf8fbc708e22e1e6328686452469d58c72d8a68ccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 42400
the chainentry 42400
- sealed to the entry before
- caef0bcf3e411b5ee85e91ac0861753a42813ded4a0e2dd80d2b54596d10280d
- this leaf
- ea249163f949472dec33f1bdbdb9afe3c78b089d0f3c48f4717779f4f6a12815
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 1o8Il+urWksstknMm51+UU/hWpDCKgpJ2gOo/jKaVJT/N0kMhneZfM9DiGQjsaWQSpoHWm/7aWcX3EVW9986Bg==