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: 2c75484980e5256a4d2529b6bebb97fedb59a405b16bcf9722103e1c3a5c6b15
Tx prefix hash: 53d77791d72361d0676081c2dd58e3df49a1778acc1b1d8e0ae7560833b5bd6a
Tx public key: c76dcfd3de1aa20474fb4d87e24862cf5ef7b62fd1e0af1780c40a0f684d2a8d
| Timestamp: 1780863162 | Timestamp [UTC]: 2026-06-07 20:12:42 | Age [y:d:h:m:s]: 00:001:04:34:05 |
| Block: 7638 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 248 | RingCT/type: yes/0 |
| Extra: 01c76dcfd3de1aa20474fb4d87e24862cf5ef7b62fd1e0af1780c40a0f684d2a8d020900000001e49593ff00 | ||
1 output(s) for total of 34.675575875770 HMNY
| stealth address | amount | amount idx | tag |
| 00: f4a34aa86febb5562991694048b164c0bb5abf928266cb623a24ddeb6813d050 | 34.675575875770 | 9442 of 0 | <77> |
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": 7698,
"vin": [ {
"gen": {
"height": 7638
}
}
],
"vout": [ {
"amount": 34675575875770,
"target": {
"tagged_key": {
"key": "f4a34aa86febb5562991694048b164c0bb5abf928266cb623a24ddeb6813d050",
"view_tag": "77"
}
}
}
],
"extra": [ 1, 199, 109, 207, 211, 222, 26, 162, 4, 116, 251, 77, 135, 226, 72, 98, 207, 94, 247, 182, 47, 209, 224, 175, 23, 128, 196, 10, 15, 104, 77, 42, 141, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}