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: 3be7dd7b648dbb10c468518c73296aaad3075836f45c808322ab2f6b7c37d9c8
Tx prefix hash: 5522627b98b7db2fa849fa319584f34b6234e4fdd2fbad9f748097d5dbbd8e34
Tx public key: 4ee3ef02f1279d118346c61a932f76a54570f2390fa4d456f576a74553cef0d3
| Timestamp: 1780830666 | Timestamp [UTC]: 2026-06-07 11:11:06 | Age [y:d:h:m:s]: 00:001:14:24:51 |
| Block: 7334 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 552 | RingCT/type: yes/0 |
| Extra: 014ee3ef02f1279d118346c61a932f76a54570f2390fa4d456f576a74553cef0d3020900000001e49593ff00 | ||
1 output(s) for total of 34.704737002496 HMNY
| stealth address | amount | amount idx | tag |
| 00: d0341a1d321d68711d0fd201bf865499ece1d5833b184d19bc6e151bebab3e8d | 34.704737002496 | 9028 of 0 | <74> |
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": 7394,
"vin": [ {
"gen": {
"height": 7334
}
}
],
"vout": [ {
"amount": 34704737002496,
"target": {
"tagged_key": {
"key": "d0341a1d321d68711d0fd201bf865499ece1d5833b184d19bc6e151bebab3e8d",
"view_tag": "74"
}
}
}
],
"extra": [ 1, 78, 227, 239, 2, 241, 39, 157, 17, 131, 70, 198, 26, 147, 47, 118, 165, 69, 112, 242, 57, 15, 164, 212, 86, 245, 118, 167, 69, 83, 206, 240, 211, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}