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: f547d56d5ecf4a5a22276a4ff2269ed0321ef4b067b3c7075a01a6be2cc769c0
Tx prefix hash: 9a606674542c7d741494593e370f732aa8ad7a946db045134f0e2d76baa209a8
Tx public key: 3014786bca085aee1a1f7c290c3a0c7295545f612a13e68d615142f35d808953
| Timestamp: 1779988763 | Timestamp [UTC]: 2026-05-28 17:19:23 | Age [y:d:h:m:s]: 00:011:08:16:34 |
| Block: 3976 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3910 | RingCT/type: yes/0 |
| Extra: 013014786bca085aee1a1f7c290c3a0c7295545f612a13e68d615142f35d80895302090000000126697be300 | ||
1 output(s) for total of 34.921243591259 HMNY
| stealth address | amount | amount idx | tag |
| 00: 2b259f82c8b0c494536d3a063c08b454a1e3cd235fe327ad5236d5e5e84eccb7 | 34.921243591259 | 4906 of 0 | <4d> |
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": 4036,
"vin": [ {
"gen": {
"height": 3976
}
}
],
"vout": [ {
"amount": 34921243591259,
"target": {
"tagged_key": {
"key": "2b259f82c8b0c494536d3a063c08b454a1e3cd235fe327ad5236d5e5e84eccb7",
"view_tag": "4d"
}
}
}
],
"extra": [ 1, 48, 20, 120, 107, 202, 8, 90, 238, 26, 31, 124, 41, 12, 58, 12, 114, 149, 84, 95, 97, 42, 19, 230, 141, 97, 81, 66, 243, 93, 128, 137, 83, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}