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: d1897ac800d676e9e52c51a21308e34fa21322a655665a2e977d4ea3b7fb1ce7
Tx prefix hash: c670597eb86723ebfd95892800cdc7e8b62c09f834d98ec938d81f25b5b4cbf0
Tx public key: 346c6665f919590f38e66ef458963ef3a634f58c8e07a79617b71d3c98473faf
| Timestamp: 1779447186 | Timestamp [UTC]: 2026-05-22 10:53:06 | Age [y:d:h:m:s]: 00:017:14:42:51 |
| Block: 280 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 7606 | RingCT/type: yes/0 |
| Extra: 01346c6665f919590f38e66ef458963ef3a634f58c8e07a79617b71d3c98473faf0209000000034438f87f00 | ||
1 output(s) for total of 35.165653678983 HMNY
| stealth address | amount | amount idx | tag |
| 00: 09ba0c404d7b2911b3c0810a5a36714e02ae9b3b6d5ea44770291c3a28bcd4b7 | 35.165653678983 | 276 of 0 | <1c> |
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": 340,
"vin": [ {
"gen": {
"height": 280
}
}
],
"vout": [ {
"amount": 35165653678983,
"target": {
"tagged_key": {
"key": "09ba0c404d7b2911b3c0810a5a36714e02ae9b3b6d5ea44770291c3a28bcd4b7",
"view_tag": "1c"
}
}
}
],
"extra": [ 1, 52, 108, 102, 101, 249, 25, 89, 15, 56, 230, 110, 244, 88, 150, 62, 243, 166, 52, 245, 140, 142, 7, 167, 150, 23, 183, 29, 60, 152, 71, 63, 175, 2, 9, 0, 0, 0, 3, 68, 56, 248, 127, 0
],
"rct_signatures": {
"type": 0
}
}