why1 reason
spend_windowspend_window_exceeded
this would take GCJMFSNQBSHTAQJOVWHBVKM4VHVGTVO5UFU5NAXGJGPEWWHAURREGTED to 30 over the last 60000ms, above the 12 window cap, with 0 already spent
what it was decided fromfingerprints
- rule compiled from it
- 08db432e743e1ff9eff8b1c677fd48acd011386d1ae7fb2de467c6061dd27436
- request
- cb4e9de7e71d597995364250629630f0e6f8854e87cb8dd458b00bec97a657b4
- transaction
- 8b2ac00fc181de3863411605bf2d6451311c40df752bf1f2dc3753a4fa2507bacomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 31630
the chainentry 31630
- sealed to the entry before
- a45cfbb5fdc0eb0057a656baa1af7b9d24b10f7c4d6ff292fef59d70fe4d3dd4
- this leaf
- 63474d1d665d292ec76bfdb79ec11cd5a17addcdca7a837fa8773f45a968bec0
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 6ZCpgJ2l8PfYQzWmbgkpme4ECQPSzbGwrdr9bV8VmJe5DzSynYSudm3JXIth7mRbGomGtR76JNfqWX18ibafDw==