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: f73e075f1bc85433c8f646328c3526eb9d15e95f069d5b208704f81d3a44e6fe
Tx prefix hash: de0240413d4b54c59d648aa4eea9fa3002e9b713302c8645e20414920f360dae
Tx public key: 8029a50038a6f0d5b8052ce85e830ee181d3222190f47cd992afac7ed2c6a3e9
| Timestamp: 1780856464 | Timestamp [UTC]: 2026-06-07 18:21:04 | Age [y:d:h:m:s]: 00:001:06:25:43 |
| Block: 7574 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 312 | RingCT/type: yes/0 |
| Extra: 018029a50038a6f0d5b8052ce85e830ee181d3222190f47cd992afac7ed2c6a3e9020900000001e49593ff00 | ||
1 output(s) for total of 34.679808996554 HMNY
| stealth address | amount | amount idx | tag |
| 00: 0ace3a68280c268b32683fc112f82856d506e11ef27e15345311df05665fedc8 | 34.679808996554 | 9356 of 0 | <41> |
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": 7634,
"vin": [ {
"gen": {
"height": 7574
}
}
],
"vout": [ {
"amount": 34679808996554,
"target": {
"tagged_key": {
"key": "0ace3a68280c268b32683fc112f82856d506e11ef27e15345311df05665fedc8",
"view_tag": "41"
}
}
}
],
"extra": [ 1, 128, 41, 165, 0, 56, 166, 240, 213, 184, 5, 44, 232, 94, 131, 14, 225, 129, 211, 34, 33, 144, 244, 124, 217, 146, 175, 172, 126, 210, 198, 163, 233, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}