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: d223d48c39919d2eb521ad691e72b70bd2da767bfa2b499102fd466b9e902629
Tx prefix hash: 67304f34004bce13dfb506c14ba277c7b8ffa8057a64a9d86d4f4b7329e908f6
Tx public key: 587d25c5b272db156b690f22e3485524f026943e7b8669e7070013886bea6799
| Timestamp: 1780690083 | Timestamp [UTC]: 2026-06-05 20:08:03 | Age [y:d:h:m:s]: 00:003:05:27:54 |
| Block: 5633 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2253 | RingCT/type: yes/0 |
| Extra: 01587d25c5b272db156b690f22e3485524f026943e7b8669e7070013886bea6799020900000001e49593ff00 | ||
1 output(s) for total of 34.808437403880 HMNY
| stealth address | amount | amount idx | tag |
| 00: 31b04a3d0cf7c3913faa829f94b93c51edd6d6966b63a8e38b1903a8817083c6 | 34.808437403880 | 7080 of 0 | <d7> |
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": 5693,
"vin": [ {
"gen": {
"height": 5633
}
}
],
"vout": [ {
"amount": 34808437403880,
"target": {
"tagged_key": {
"key": "31b04a3d0cf7c3913faa829f94b93c51edd6d6966b63a8e38b1903a8817083c6",
"view_tag": "d7"
}
}
}
],
"extra": [ 1, 88, 125, 37, 197, 178, 114, 219, 21, 107, 105, 15, 34, 227, 72, 85, 36, 240, 38, 148, 62, 123, 134, 105, 231, 7, 0, 19, 136, 107, 234, 103, 153, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}