why1 reason
spend_windowspend_window_exceeded
this would take GD3LBPHRDVQ4NACGNOTHTDFAFB7JPD3WODASKJLTALL3SEK5MTC7MCGG to 30 over the last 60000ms, above the 12 window cap, with 0 already spent
what it was decided fromfingerprints
- rule compiled from it
- be38e29ec8276b300f12dc55b26245713944fa4740a5073877113472fe28dde6
- request
- 199b90010c583703f8d484af268ff55a08b03dc4171374795a3b07b2dbf86f00
- transaction
- 6cc629bf11c35f0d506fe1087e05eb92cdce0fdd56a9fb1e1476757607ca294fcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 44204
the chainentry 44204
- sealed to the entry before
- 804cef5fd8fc815cd75115433e7da28d88392e1af0ea5ef6c3baf4e47777577a
- this leaf
- 58b1a7e6eb0e63072551262cbefe83c288ac6f99b0f8335a66a65c29acfd11cb
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- B49fjMvPm4kGLV9uoso8clKDHTMfwtRc+1tK8ML2GDvbS0F5GTrcX4oJesoFfu8m3vYdp0XxRb26Oeo4gXmrDg==