For RingCT transactions, outputs' amounts are also decoded
Tx private key can be obtained using get_tx_key
command in hashmonkey-wallet-cli command line tool
Tx hash: b4f2e4dffe31519099130ad35e0a68d78433d51f042dc6b965c5ce5799a334ff
Tx prefix hash: b212b82c2fc06be76073078a7b5634e01f7482c24bb506f24256c1a1f6f1b47c
Tx public key: 00e803cd8a214cd3ede91bfab24e5bfbf709eb99e8f4a41ab12a3a72a1358c2a
| Timestamp: 1780776780 | Timestamp [UTC]: 2026-06-06 20:13:00 | Age [y:d:h:m:s]: 00:002:03:05:53 |
| Block: 6730 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1156 | RingCT/type: yes/0 |
| Extra: 0100e803cd8a214cd3ede91bfab24e5bfbf709eb99e8f4a41ab12a3a72a1358c2a020900000003e49593ff00 | ||
1 output(s) for total of 34.735681644146 HMNY
| stealth address | amount | amount idx | tag |
| 00: eb5275b1e5a56f85e96e1d6f66f854e82f9cde91ae65e6a9acdc6191ec3f517c | 34.735681644146 | 8302 of 0 | <57> |
Check which outputs belong to given HMNY address/subaddress and viewkey
For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side
Prove to someone that you have sent them HMNY in this transaction
Tx private key can be obtained using get_tx_key
command in hashmonkey-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side
{
"version": 2,
"unlock_time": 6790,
"vin": [ {
"gen": {
"height": 6730
}
}
],
"vout": [ {
"amount": 34735681644146,
"target": {
"tagged_key": {
"key": "eb5275b1e5a56f85e96e1d6f66f854e82f9cde91ae65e6a9acdc6191ec3f517c",
"view_tag": "57"
}
}
}
],
"extra": [ 1, 0, 232, 3, 205, 138, 33, 76, 211, 237, 233, 27, 250, 178, 78, 91, 251, 247, 9, 235, 153, 232, 244, 164, 26, 177, 42, 58, 114, 161, 53, 140, 42, 2, 9, 0, 0, 0, 3, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}