why1 reason
spend_windowspend_window_exceeded
this would take GCIOB6NZ6BC2IZOCJJ6Q6L33H57ZHUYI2M3NFHY4MJSZH32SUJYMJI56 to 30 over the last 60000ms, above the 12 window cap, with 0 already spent
what it was decided fromfingerprints
- rule compiled from it
- c29c3bf7261301a4255c7ad8b464f0594874a6e0f2ffc5bd6c781643021de642
- request
- 7c2efbdf5f56a8156eb54a6334b76ed63fa0fcc3f89895f03cfd62e08b7cfbee
- transaction
- e1d46a71c68696ce8c29937624275f7396fcb3544972cf3b2cf2297e29c11b0ecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 27014
the chainentry 27014
- sealed to the entry before
- c3b4d14f47504f0f294f812b84e55321b807a395e032862b749e1ac97ea02b5f
- this leaf
- c674fc6e4eaa4020b1ef5c40a26779c1efdd470c5fa3a1b002bfb4d3acaa3f0c
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- ZNpfjALxduGmgfu20FdS3h/HgxCtgJJ6L7eypSXMi1JfUkXWV4F8+XNifVM3IZyt7fMy3vwj69ltOXM2blJJDQ==