From 8b87f7aecf8d5d9e5e78362c68bb7062c88b1367 Mon Sep 17 00:00:00 2001
From: necrashter
Date: Sun, 24 Apr 2022 22:21:40 +0300
Subject: Example serialization for mining

---
 content/block_docs.md | 4 ++++
 1 file changed, 4 insertions(+)

(limited to 'content')

diff --git a/content/block_docs.md b/content/block_docs.md
index 3c47231..963db68 100644
--- a/content/block_docs.md
+++ b/content/block_docs.md
@@ -49,6 +49,10 @@ The _mining_ process for the hash involves;
 - Serializing it
     - **NOTE:** Serialized JSON must comply with the rules explained in hash section of [transaction](@/transaction_docs.md) page.
     - The order of keys should be as follows: `transaction_list`, `nonce`, `timestamp`.
+	- Example:
+```json
+{"transaction_list":["a1a3","cde4","60e7","4e04"],"nonce":5342433,"timestamp":"2022-04-23T23:49:24.622651"}
+```
 - Calculating blake2s hash of the serialized string
 - Checking if the hash is valid
     - The hash is considered valid if its hexadecimal representation starts with an arbitrary number of zeros.
-- 
cgit v1.2.3-70-g09d2