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: bee28e70f72ae6b44e0324ad88d29f0f773929490e5074c16536560082946056
Tx prefix hash: 82c4ba96c67eabf0af44620fa541ed773d0fcd385c9b38f5c538b00a85764824
Tx public key: bb564c0984a6cf949de1c0883c07426e9c6a629434c15a4e81bda80ab361e163
| Timestamp: 1780051669 | Timestamp [UTC]: 2026-05-29 10:47:49 | Age [y:d:h:m:s]: 00:010:16:01:59 |
| Block: 4406 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3503 | RingCT/type: yes/0 |
| Extra: 01bb564c0984a6cf949de1c0883c07426e9c6a629434c15a4e81bda80ab361e16302090000000326697be300 | ||
1 output(s) for total of 34.889995650380 HMNY
| stealth address | amount | amount idx | tag |
| 00: 2c8cad0e15dca4c74b475f5aba4b887800a48fea5f3d356c76058555f12de21e | 34.889995650380 | 5511 of 0 | <3e> |
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": 4466,
"vin": [ {
"gen": {
"height": 4406
}
}
],
"vout": [ {
"amount": 34889995650380,
"target": {
"tagged_key": {
"key": "2c8cad0e15dca4c74b475f5aba4b887800a48fea5f3d356c76058555f12de21e",
"view_tag": "3e"
}
}
}
],
"extra": [ 1, 187, 86, 76, 9, 132, 166, 207, 148, 157, 225, 192, 136, 60, 7, 66, 110, 156, 106, 98, 148, 52, 193, 90, 78, 129, 189, 168, 10, 179, 97, 225, 99, 2, 9, 0, 0, 0, 3, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}