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: ce44508fec65d86acd9ce58945d63d7147a431ab5090c855ed54557b037f47a9
Tx prefix hash: 4f0fb452e227fcc306c77e3e40f2c975ca15c7078d169df2b2b9c6c2180cad4d
Tx public key: 8963c7a1acb1677b9084962e46e5d12ae33fa2297c615b35fdc7aa576bd1a1b1
| Timestamp: 1780025903 | Timestamp [UTC]: 2026-05-29 03:38:23 | Age [y:d:h:m:s]: 00:010:23:11:25 |
| Block: 4169 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3730 | RingCT/type: yes/0 |
| Extra: 018963c7a1acb1677b9084962e46e5d12ae33fa2297c615b35fdc7aa576bd1a1b102090000000626697be300 | ||
1 output(s) for total of 34.905770961069 HMNY
| stealth address | amount | amount idx | tag |
| 00: 9bf4a8900751c3aa5c38b6621a54096dd287820dd8ad7adcb8b4849995949bed | 34.905770961069 | 5202 of 0 | <1b> |
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": 4229,
"vin": [ {
"gen": {
"height": 4169
}
}
],
"vout": [ {
"amount": 34905770961069,
"target": {
"tagged_key": {
"key": "9bf4a8900751c3aa5c38b6621a54096dd287820dd8ad7adcb8b4849995949bed",
"view_tag": "1b"
}
}
}
],
"extra": [ 1, 137, 99, 199, 161, 172, 177, 103, 123, 144, 132, 150, 46, 70, 229, 209, 42, 227, 63, 162, 41, 124, 97, 91, 53, 253, 199, 170, 87, 107, 209, 161, 177, 2, 9, 0, 0, 0, 6, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}