why1 reason
spend_windowspend_window_exceeded
this would take GBLBD36KZOYVQ3IAUPNSDE6RMBI6DOFOALXNS3TEC753FMRBNNVL5S5I to 30 over the last 60000ms, above the 12 window cap, with 0 already spent
what it was decided fromfingerprints
- rule compiled from it
- a49362c10ac61496c111c1eb6bec2839064560c7036e0d38c9a7b7b65b09e618
- request
- e4afe52a4e4528ab7f67c37b93300215974460cbfbab31898cb1d885b3288ff3
- transaction
- 4f8b61d201ef709c334683e8a824d46c56e9185a6b9040f0df038cffa7b8555bcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 50503
the chainentry 50503
- sealed to the entry before
- 6c8bee7e88c532342cc29704788f5cf41a03183ad8ed8115bf0f3fd25fe4389e
- this leaf
- 1536178e6f706ad175835cfbd4530c5bcad5bd2ca61cfc7bf449a0d7b269a9e6
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- LJ0074UcA9uJwtEe9pRAn0ulw9k64r0AnfH4twHLvEoZIj9/pbAn/189N6WeBM4dUn7N0OkgTdgpandkpmk0Cg==