why1 reason
spend_windowspend_window_exceeded
this would take GB5Q54RH6I5RIW6RV2X3OXN7X7E2AG7DMTNPIWYRFA4DMDGVZJWFC6TR to 108 over the last 60000ms, above the 90 window cap, with 78 already spent
what it was decided fromfingerprints
- rule compiled from it
- 804eb8e59a7ebaf653bb11638f578ac5640c2d77934b19a17ff974c7cdae9acd
- request
- a8a37e81b059c0c50b7c9425131722903b470464a29cc0a0a5e2313734d17e5b
- transaction
- 42127ef9f689642b01b18464a2b03d3ecef640ed0cda07bdbf36a770200de61ecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 75810
the chainentry 75810
- sealed to the entry before
- 34b929a835fd25d9312f78a9ffe65bcd5b863a1a2e8f7528ad253fb4bb1b78cf
- this leaf
- 4baa5645673c7ec451af7cea99715f4bd239d01a51e1dc5c06f081b1a3f6be86
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- B9esnLVFKoWRLr8Tl8R8dfYD2z/Qtbj9EMcL48TIeEi9pE2IUV7uJH2521/dLezkBRh014GMzUnpNd4Hig30Dw==