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: 125ca71bd56dde72232c3b2a3a910f63eecdb06bca35e0abf70ad79cf26f0e58
Tx prefix hash: f4726a7440b24769503472ee945bc9d040ec97c0ec59bf79f1983660b1c56f3b
Tx public key: 4c4b901904e0c478af73643d4b5d0bc31e8732525d8be662f71d8e01b4f6decf
| Timestamp: 1780835417 | Timestamp [UTC]: 2026-06-07 12:30:17 | Age [y:d:h:m:s]: 00:001:09:54:32 |
| Block: 7399 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 487 | RingCT/type: yes/0 |
| Extra: 014c4b901904e0c478af73643d4b5d0bc31e8732525d8be662f71d8e01b4f6decf020900000001e49593ff00 | ||
1 output(s) for total of 34.698808574803 HMNY
| stealth address | amount | amount idx | tag |
| 00: 9a6228db6e826b7687ac61286597cace28318049b6614fe53a1f03cc48ff47ca | 34.698808574803 | 9109 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": 7459,
"vin": [ {
"gen": {
"height": 7399
}
}
],
"vout": [ {
"amount": 34698808574803,
"target": {
"tagged_key": {
"key": "9a6228db6e826b7687ac61286597cace28318049b6614fe53a1f03cc48ff47ca",
"view_tag": "ea"
}
}
}
],
"extra": [ 1, 76, 75, 144, 25, 4, 224, 196, 120, 175, 115, 100, 61, 75, 93, 11, 195, 30, 135, 50, 82, 93, 139, 230, 98, 247, 29, 142, 1, 180, 246, 222, 207, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}