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: f240fd602ac774f9b1ca8c345cb7ba6d7ad6b55140a58838335c1788e6ef469c
Tx prefix hash: db0b1ed8edfbf4fed163a6e6482fe47b5e04e445f13199712a7a82daf99cec38
Tx public key: 5a83a99ac4e3cf23197e37d6cf60a59ca0ebb7559e670e56c706068dd6722bc0
| Timestamp: 1779455675 | Timestamp [UTC]: 2026-05-22 13:14:35 | Age [y:d:h:m:s]: 00:017:10:04:18 |
| Block: 380 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 7506 | RingCT/type: yes/0 |
| Extra: 015a83a99ac4e3cf23197e37d6cf60a59ca0ebb7559e670e56c706068dd6722bc002090000000193369e7d00 | ||
1 output(s) for total of 35.158946996060 HMNY
| stealth address | amount | amount idx | tag |
| 00: ca14ef77b3090b32e50a6b588d25a808b5124263bf1a6a1b956d08f4756578d4 | 35.158946996060 | 378 of 0 | <3e> |
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": 440,
"vin": [ {
"gen": {
"height": 380
}
}
],
"vout": [ {
"amount": 35158946996060,
"target": {
"tagged_key": {
"key": "ca14ef77b3090b32e50a6b588d25a808b5124263bf1a6a1b956d08f4756578d4",
"view_tag": "3e"
}
}
}
],
"extra": [ 1, 90, 131, 169, 154, 196, 227, 207, 35, 25, 126, 55, 214, 207, 96, 165, 156, 160, 235, 183, 85, 158, 103, 14, 86, 199, 6, 6, 141, 214, 114, 43, 192, 2, 9, 0, 0, 0, 1, 147, 54, 158, 125, 0
],
"rct_signatures": {
"type": 0
}
}