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: d06e599c935c203800582765f0f4d8abdec31525024eeb5b0e6676a159be3213
Tx prefix hash: c5bc468c363ee0ff2bcdf924908c4b2143fab15d46f3026c6c1fb8c0a0735b46
Tx public key: 344741f5a761ea29bf4c49d72e876a42040e7aedcd3842f82492176ba8416b7f
| Timestamp: 1780713384 | Timestamp [UTC]: 2026-06-06 02:36:24 | Age [y:d:h:m:s]: 00:002:22:59:33 |
| Block: 6173 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1713 | RingCT/type: yes/0 |
| Extra: 01344741f5a761ea29bf4c49d72e876a42040e7aedcd3842f82492176ba8416b7f020900000001e49593ff00 | ||
1 output(s) for total of 34.772604240619 HMNY
| stealth address | amount | amount idx | tag |
| 00: 9e51fc1b8817b1ed3a2bfe5ea9bdf4c8d09696110da8b5e21af4d8daf81f3c1b | 34.772604240619 | 7650 of 0 | <25> |
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": 6233,
"vin": [ {
"gen": {
"height": 6173
}
}
],
"vout": [ {
"amount": 34772604240619,
"target": {
"tagged_key": {
"key": "9e51fc1b8817b1ed3a2bfe5ea9bdf4c8d09696110da8b5e21af4d8daf81f3c1b",
"view_tag": "25"
}
}
}
],
"extra": [ 1, 52, 71, 65, 245, 167, 97, 234, 41, 191, 76, 73, 215, 46, 135, 106, 66, 4, 14, 122, 237, 205, 56, 66, 248, 36, 146, 23, 107, 168, 65, 107, 127, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}