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: d2b05484372939654bd35523bde118f709084dcfc2e089a7a0b1e0f9e9d6d8df
Tx prefix hash: e23ac794f990fea97ccb6fa150aee6ebd78cfa419915f5cc690a38e1f27efcda
Tx public key: d0e8b2b7659b20e3a84462b2dce1fdefe637b89cac0a6da7d6501c6716d37240
| Timestamp: 1780706762 | Timestamp [UTC]: 2026-06-06 00:46:02 | Age [y:d:h:m:s]: 00:003:00:49:55 |
| Block: 6119 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1767 | RingCT/type: yes/0 |
| Extra: 01d0e8b2b7659b20e3a84462b2dce1fdefe637b89cac0a6da7d6501c6716d37240020900000003e49593ff00 | ||
1 output(s) for total of 34.776185896355 HMNY
| stealth address | amount | amount idx | tag |
| 00: 322d8300bc147c95c50974b6b0d1deb9c5b58833a0b06ba3b0871de41f642e13 | 34.776185896355 | 7592 of 0 | <08> |
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": 6179,
"vin": [ {
"gen": {
"height": 6119
}
}
],
"vout": [ {
"amount": 34776185896355,
"target": {
"tagged_key": {
"key": "322d8300bc147c95c50974b6b0d1deb9c5b58833a0b06ba3b0871de41f642e13",
"view_tag": "08"
}
}
}
],
"extra": [ 1, 208, 232, 178, 183, 101, 155, 32, 227, 168, 68, 98, 178, 220, 225, 253, 239, 230, 55, 184, 156, 172, 10, 109, 167, 214, 80, 28, 103, 22, 211, 114, 64, 2, 9, 0, 0, 0, 3, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}