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: 03a5758ed543ff0622bad6cc284b8c6ca46bbb1504a27a184fdbd363c6b12567
Tx prefix hash: 2b6c7ab102cfe4af44660c5b97cfe969fd39b8ae094a9b78d871cc5ec6431dbf
Tx public key: 146e725fda8b04d37efd3b39811230882eb29b75cc029eba0c9f49a9bf2f45fd
| Timestamp: 1779724392 | Timestamp [UTC]: 2026-05-25 15:53:12 | Age [y:d:h:m:s]: 00:014:11:57:46 |
| Block: 1823 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 6127 | RingCT/type: yes/0 |
| Extra: 01146e725fda8b04d37efd3b39811230882eb29b75cc029eba0c9f49a9bf2f45fd020900000003ba6d17be00 | ||
1 output(s) for total of 35.062311836410 HMNY
| stealth address | amount | amount idx | tag |
| 00: 6c564dc1238a9c28ea51035e02f51803282bf5915ea7f316e4170fe681ea9741 | 35.062311836410 | 2017 of 0 | <d2> |
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": 1883,
"vin": [ {
"gen": {
"height": 1823
}
}
],
"vout": [ {
"amount": 35062311836410,
"target": {
"tagged_key": {
"key": "6c564dc1238a9c28ea51035e02f51803282bf5915ea7f316e4170fe681ea9741",
"view_tag": "d2"
}
}
}
],
"extra": [ 1, 20, 110, 114, 95, 218, 139, 4, 211, 126, 253, 59, 57, 129, 18, 48, 136, 46, 178, 155, 117, 204, 2, 158, 186, 12, 159, 73, 169, 191, 47, 69, 253, 2, 9, 0, 0, 0, 3, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}