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: 582502741f12b8d4398bf9d01169237ea95208752e16fb81f18599b8d69df527
Tx prefix hash: 3072f78eb7c4a260844f0d45458814567ae8a2568f0b662f6e9f5631d577a71d
Tx public key: c30897393ab819510eaded3a0a56628a973597601aa1c8298d523633ea37184d
| Timestamp: 1779451584 | Timestamp [UTC]: 2026-05-22 12:06:24 | Age [y:d:h:m:s]: 00:017:15:32:26 |
| Block: 334 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 7613 | RingCT/type: yes/0 |
| Extra: 01c30897393ab819510eaded3a0a56628a973597601aa1c8298d523633ea37184d0209000000024438f87f00 | ||
1 output(s) for total of 35.162031911328 HMNY
| stealth address | amount | amount idx | tag |
| 00: 73be6fcac69bcb8a2e3b26460f608982bc8bfd13e2f26a03b73be37cbbce6c1f | 35.162031911328 | 330 of 0 | <b9> |
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": 394,
"vin": [ {
"gen": {
"height": 334
}
}
],
"vout": [ {
"amount": 35162031911328,
"target": {
"tagged_key": {
"key": "73be6fcac69bcb8a2e3b26460f608982bc8bfd13e2f26a03b73be37cbbce6c1f",
"view_tag": "b9"
}
}
}
],
"extra": [ 1, 195, 8, 151, 57, 58, 184, 25, 81, 14, 173, 237, 58, 10, 86, 98, 138, 151, 53, 151, 96, 26, 161, 200, 41, 141, 82, 54, 51, 234, 55, 24, 77, 2, 9, 0, 0, 0, 2, 68, 56, 248, 127, 0
],
"rct_signatures": {
"type": 0
}
}