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: 22aea73c22338e1e73bd81060b47f33914da1db31bc8e356c21c52870433f02f
Tx prefix hash: da8239652efc67cf4d67eaa00f86f9ccd2b5e62c6f57cfe96ac9d369278db94d
Tx public key: 11cc2081ffaeefd9ca0498df2aba1f7219c4142981e323fbdc46421fc5be1d91
| Timestamp: 1779722984 | Timestamp [UTC]: 2026-05-25 15:29:44 | Age [y:d:h:m:s]: 00:014:12:09:06 |
| Block: 1791 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 6157 | RingCT/type: yes/0 |
| Extra: 0111cc2081ffaeefd9ca0498df2aba1f7219c4142981e323fbdc46421fc5be1d91020900000002ba6d17be00 | ||
1 output(s) for total of 35.069453537443 HMNY
| stealth address | amount | amount idx | tag |
| 00: 575f5b9bb6d8aac892797e41ced1f7b3b376cdf4e0994c6d6e334fa099509fe7 | 35.069453537443 | 1978 of 0 | <44> |
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": 1851,
"vin": [ {
"gen": {
"height": 1791
}
}
],
"vout": [ {
"amount": 35069453537443,
"target": {
"tagged_key": {
"key": "575f5b9bb6d8aac892797e41ced1f7b3b376cdf4e0994c6d6e334fa099509fe7",
"view_tag": "44"
}
}
}
],
"extra": [ 1, 17, 204, 32, 129, 255, 174, 239, 217, 202, 4, 152, 223, 42, 186, 31, 114, 25, 196, 20, 41, 129, 227, 35, 251, 220, 70, 66, 31, 197, 190, 29, 145, 2, 9, 0, 0, 0, 2, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}