why1 reason
spend_windowspend_window_exceeded
this would take GCDHYQ554WHSIIPLPXYXJGHZJSWITSTPBPMW7CMF62SUS43SFHNWFGW4 to 30 over the last 60000ms, above the 12 window cap, with 0 already spent
what it was decided fromfingerprints
- rule compiled from it
- a130a4ec63242c7fe971f2b031ede0e00fb3863a4a009efa5cbbd2b8545ae9bd
- request
- 6bf356dfa5961d71ed8776ff7f7477b814873dcf5696691831a5732287ebeb1a
- transaction
- 40f46b212ca92e80eb958db19fcd0c3db0b865694bd7dd856d4c270aeb221c5ccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 4653
the chainentry 4653
- sealed to the entry before
- e1c1346f26658b13b36df19c1f87e46c503b4b79fd89d20a0f95d8f668f72433
- this leaf
- 29d9b890e77cb3fd32e8edab2d7d85f7ac57b0d10a253071750b499cf3b1e8ae
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- P434UNI7iZgRHEhMXYi5t6u56vULrA0WjYKGLsd1UgvbF52Xnvo/KOo1ByBAU2nvB6ICTQNAV7PXMwMv8qPJCg==