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: 1344623b7d868fc1dabf060341bb87ae86f2bd289cc72955bf983d71df953b84
Tx prefix hash: af1a279705b08b8e1dfbc5a5ffdaddf07ac16bd829edb0d956df8df9bc7fa16f
Tx public key: 3512fdb9a92a799f3a6fad14445b98948d84bc171b0f9025fca2eefb41705b88
| Timestamp: 1780997867 | Timestamp [UTC]: 2026-06-09 09:37:47 | Age [y:d:h:m:s]: 00:000:06:21:57 |
| Block: 8386 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 305 | RingCT/type: yes/0 |
| Extra: 013512fdb9a92a799f3a6fad14445b98948d84bc171b0f9025fca2eefb41705b88020900000001e49593ff00 | ||
1 output(s) for total of 34.626139569964 HMNY
| stealth address | amount | amount idx | tag |
| 00: 5493712866f7c737083085d35c2d674e47d559abcc7ca3a8291dbe8b1adc6bfe | 34.626139569964 | 10366 of 0 | <cb> |
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": 8446,
"vin": [ {
"gen": {
"height": 8386
}
}
],
"vout": [ {
"amount": 34626139569964,
"target": {
"tagged_key": {
"key": "5493712866f7c737083085d35c2d674e47d559abcc7ca3a8291dbe8b1adc6bfe",
"view_tag": "cb"
}
}
}
],
"extra": [ 1, 53, 18, 253, 185, 169, 42, 121, 159, 58, 111, 173, 20, 68, 91, 152, 148, 141, 132, 188, 23, 27, 15, 144, 37, 252, 162, 238, 251, 65, 112, 91, 136, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}