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: 9ba757c115c4e058608d704c362452d3296c1dd8efd079a48bf88ac96f321834
Tx prefix hash: 3b5ad5fbd49e44676da85f08d5b5c5027da817f60b35f1e93b27c89dcce725e3
Tx public key: eb2a49103b7971adc0e7b0ea43a629c350f2d110a66a068787b0bd3e5f2b8416
| Timestamp: 1780901229 | Timestamp [UTC]: 2026-06-08 06:47:09 | Age [y:d:h:m:s]: 00:000:18:48:48 |
| Block: 7815 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 71 | RingCT/type: yes/0 |
| Extra: 01eb2a49103b7971adc0e7b0ea43a629c350f2d110a66a068787b0bd3e5f2b84160209000000014a728a4c00 | ||
1 output(s) for total of 34.663871341482 HMNY
| stealth address | amount | amount idx | tag |
| 00: 0b3d5a21b95c323708314b57968cca58b09c9d1c4a88e96200fb97b637d1a90c | 34.663871341482 | 9687 of 0 | <46> |
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": 7875,
"vin": [ {
"gen": {
"height": 7815
}
}
],
"vout": [ {
"amount": 34663871341482,
"target": {
"tagged_key": {
"key": "0b3d5a21b95c323708314b57968cca58b09c9d1c4a88e96200fb97b637d1a90c",
"view_tag": "46"
}
}
}
],
"extra": [ 1, 235, 42, 73, 16, 59, 121, 113, 173, 192, 231, 176, 234, 67, 166, 41, 195, 80, 242, 209, 16, 166, 106, 6, 135, 135, 176, 189, 62, 95, 43, 132, 22, 2, 9, 0, 0, 0, 1, 74, 114, 138, 76, 0
],
"rct_signatures": {
"type": 0
}
}