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: 3c566822316adaac8469de7e131a8a1d41ba3bb3673304941578ab88800e9e7c
Tx prefix hash: 3e947464dc685b901d8a2baabef54d6250ffcbf4d436528d143ea6ec429982d7
Tx public key: 4f00f3d52e4941d03959bb45bca40f993ef7e228609f888ccc8a947c1b1b94cb
| Timestamp: 1780726076 | Timestamp [UTC]: 2026-06-06 06:07:56 | Age [y:d:h:m:s]: 00:002:19:28:01 |
| Block: 6274 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1612 | RingCT/type: yes/0 |
| Extra: 014f00f3d52e4941d03959bb45bca40f993ef7e228609f888ccc8a947c1b1b94cb020900000001e49593ff00 | ||
1 output(s) for total of 34.765906208019 HMNY
| stealth address | amount | amount idx | tag |
| 00: 7622b20ce2db0061b58d5b7e7a669c9dcbc6ee2b0b7c50e5d1167fc5ba6740b9 | 34.765906208019 | 7757 of 0 | <3d> |
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": 6334,
"vin": [ {
"gen": {
"height": 6274
}
}
],
"vout": [ {
"amount": 34765906208019,
"target": {
"tagged_key": {
"key": "7622b20ce2db0061b58d5b7e7a669c9dcbc6ee2b0b7c50e5d1167fc5ba6740b9",
"view_tag": "3d"
}
}
}
],
"extra": [ 1, 79, 0, 243, 213, 46, 73, 65, 208, 57, 89, 187, 69, 188, 164, 15, 153, 62, 247, 226, 40, 96, 159, 136, 140, 204, 138, 148, 124, 27, 27, 148, 203, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}