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: de0dfc1de88c5615d34fc8441e80e81aea03d201e01e8efe8c9e760fc32eb1c4
Tx prefix hash: fd6021cef5b22199cb50a14c08418ee55c7c8c4391780855605f253389485033
Tx public key: cf89aad5420347a053ab51abdab29e4b2d9fff7601be162c810e587dfc22ad54
| Timestamp: 1779951239 | Timestamp [UTC]: 2026-05-28 06:53:59 | Age [y:d:h:m:s]: 00:011:19:55:49 |
| Block: 3630 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4290 | RingCT/type: yes/0 |
| Extra: 01cf89aad5420347a053ab51abdab29e4b2d9fff7601be162c810e587dfc22ad5402090000000626697be300 | ||
1 output(s) for total of 34.941674706532 HMNY
| stealth address | amount | amount idx | tag |
| 00: e18e73d58e22f5f970c47bf1ba906cfea8eaa049291afb73eeeab8bb3a64d9af | 34.941674706532 | 4383 of 0 | <8a> |
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": 3690,
"vin": [ {
"gen": {
"height": 3630
}
}
],
"vout": [ {
"amount": 34941674706532,
"target": {
"tagged_key": {
"key": "e18e73d58e22f5f970c47bf1ba906cfea8eaa049291afb73eeeab8bb3a64d9af",
"view_tag": "8a"
}
}
}
],
"extra": [ 1, 207, 137, 170, 213, 66, 3, 71, 160, 83, 171, 81, 171, 218, 178, 158, 75, 45, 159, 255, 118, 1, 190, 22, 44, 129, 14, 88, 125, 252, 34, 173, 84, 2, 9, 0, 0, 0, 6, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}