why2 reasons
spend_windowspend_window_exceeded
this would take GCCVUONWSOCRRYQIU4IWNHW2TWXVZZS3VFH6FGHPWEI4U2WDSJNYK6RP to 70 over the last 60000ms, above the 12 window cap, with 0 already spent
mandateamount_exceeds_cap
op 0 pays 70.0000000, cap is 40
what it was decided fromfingerprints
- rule compiled from it
- 4f25656f4f42cd51f6b91ce0a0816540bac72ffd3bbd86aab4f296c5ecf295b8
- request
- fa11919ac183658df2f1175392e6f32cd870517bd36c85b9c2a09f89d8b12586
- transaction
- 1fbd1c3274a26abb79d82b4561dc672fe6ae5371e90b1a6fed52c9ab1c6311b9computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 44300
the chainentry 44300
- sealed to the entry before
- 5469a25083649c4893a0b5bbc7409caf03f2758a6716674ac79ad8a5938af233
- this leaf
- 8e48ee87c6a8488abe9f6c70bbec75db4eecc19a473216d10852529cf1368cd3
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- qFBFgMWLxdsJATYkJSZgqeI6C3Ua/YWZ8rVvbTLUCm8Sbxbp4bm2e7wxkI9kXZ+vBFVXKR74hQsj843nOE+NAQ==