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: 7aa34f8d7e9ad221d23e2b4be7dafb41655d85e0fba97b765160ad780e6a1805
Tx prefix hash: a742a32d96d024ce656141c3ddb9fc7102b1f04e88fbb5c6cea6265ba6e0f3e3
Tx public key: 9ab2d70b91b58bffef22a01f2efe542369772ac9903fb152c09a5a59071f3383
| Timestamp: 1780977435 | Timestamp [UTC]: 2026-06-09 03:57:15 | Age [y:d:h:m:s]: 00:000:03:56:59 |
| Block: 7955 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 294 | RingCT/type: yes/0 |
| Extra: 019ab2d70b91b58bffef22a01f2efe542369772ac9903fb152c09a5a59071f3383020900000002e49593ff00 | ||
1 output(s) for total of 34.654616316124 HMNY
| stealth address | amount | amount idx | tag |
| 00: 912ca160cbb23a5846a11f729c51b5de0935fbbe5196bcd9107f061cc07cc427 | 34.654616316124 | 9867 of 0 | <e7> |
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": 8015,
"vin": [ {
"gen": {
"height": 7955
}
}
],
"vout": [ {
"amount": 34654616316124,
"target": {
"tagged_key": {
"key": "912ca160cbb23a5846a11f729c51b5de0935fbbe5196bcd9107f061cc07cc427",
"view_tag": "e7"
}
}
}
],
"extra": [ 1, 154, 178, 215, 11, 145, 181, 139, 255, 239, 34, 160, 31, 46, 254, 84, 35, 105, 119, 42, 201, 144, 63, 177, 82, 192, 154, 90, 89, 7, 31, 51, 131, 2, 9, 0, 0, 0, 2, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}