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: 3c34103bc9d638c3c69651f0854a917c3f6380f90fe40d96894751a914235969
Tx prefix hash: abf965532a8ed89e608309dc4a6b460cce5cd2357463db0177f0992d012e4d6d
Tx public key: 6829d2783c4a71606e01b0e4362455565f0443d161b798f2c0d763cef67cb003
| Timestamp: 1780992652 | Timestamp [UTC]: 2026-06-09 08:10:52 | Age [y:d:h:m:s]: 00:008:00:25:22 |
| Block: 8263 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 482 | RingCT/type: yes/0 |
| Extra: 016829d2783c4a71606e01b0e4362455565f0443d161b798f2c0d763cef67cb003020900000002e49593ff00 | ||
1 output(s) for total of 34.634263957437 HMNY
| stealth address | amount | amount idx | tag |
| 00: 5d212f30ec3280fff3c0c696debfb948cf029a505abfa9ae897aee7f8a864600 | 34.634263957437 | 10227 of 0 | <48> |
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": 8323,
"vin": [ {
"gen": {
"height": 8263
}
}
],
"vout": [ {
"amount": 34634263957437,
"target": {
"tagged_key": {
"key": "5d212f30ec3280fff3c0c696debfb948cf029a505abfa9ae897aee7f8a864600",
"view_tag": "48"
}
}
}
],
"extra": [ 1, 104, 41, 210, 120, 60, 74, 113, 96, 110, 1, 176, 228, 54, 36, 85, 86, 95, 4, 67, 209, 97, 183, 152, 242, 192, 215, 99, 206, 246, 124, 176, 3, 2, 9, 0, 0, 0, 2, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}