why2 reasons
spend_windowspend_window_exceeded
this would take GD5EMRPMBO37GQUC6H6IOQGNZX3CUXBCNONU7FTXQIJC7IYVKWTO3K3L 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
- a0e2c2b0a77a56489d9ef8412c24b58fd964de74bdf16b68452397185145993b
- request
- c3183c23304c9d09a7c5b3b7ad27ac3ff2b64407a35917781e3caf6c1176977b
- transaction
- 5015674adb4018845aae202d4672a2ad17026bfe0fe5d07c98d80ce2a5c47ec3computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 62920
the chainentry 62920
- sealed to the entry before
- ff8f5022b65b149b29a7db962df8bb90b2e7adf14b745bcd7fcfcea2a3db69bd
- this leaf
- 0b969464a3f73269ea1229df3741b81f592b84d4152598bf2b1ae16c6631c5a4
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- q4H3CWw1VZ/wQF29m4kEoczDFrXN4skxcXsqiM737QrZf3cr3NGxWDorZi1fNTc8PYUhCL63qr/RFrF8i0DEDQ==