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: 06133921472721a13dbb28ead31662b4f2b605b48aace0af0e5b1552fb2ce526
Tx prefix hash: c4f3cf0ddb2d8b2122268defe028d74b7bf518bc27eef6722f39d427883c6ff4
Tx public key: dee1c3f6b022dc014dc48d2fed3d7615c70d6cb3850a096ed9300e0c2b0d73bf
| Timestamp: 1779724328 | Timestamp [UTC]: 2026-05-25 15:52:08 | Age [y:d:h:m:s]: 00:014:10:57:40 |
| Block: 1822 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 6098 | RingCT/type: yes/0 |
| Extra: 01dee1c3f6b022dc014dc48d2fed3d7615c70d6cb3850a096ed9300e0c2b0d73bf020900000004ba6d17be00 | ||
1 output(s) for total of 35.062378712590 HMNY
| stealth address | amount | amount idx | tag |
| 00: 6785e5bfbbe8f9725ea84cc84bbc04903386ec889a9d185d09633e56540fae10 | 35.062378712590 | 2016 of 0 | <ea> |
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": 1882,
"vin": [ {
"gen": {
"height": 1822
}
}
],
"vout": [ {
"amount": 35062378712590,
"target": {
"tagged_key": {
"key": "6785e5bfbbe8f9725ea84cc84bbc04903386ec889a9d185d09633e56540fae10",
"view_tag": "ea"
}
}
}
],
"extra": [ 1, 222, 225, 195, 246, 176, 34, 220, 1, 77, 196, 141, 47, 237, 61, 118, 21, 199, 13, 108, 179, 133, 10, 9, 110, 217, 48, 14, 12, 43, 13, 115, 191, 2, 9, 0, 0, 0, 4, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}