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: 771932aca4def0054d3f74b55eb9ce52243a40db1ee0eb2b794b5f5cff0a5308
Tx prefix hash: cf7197a6af088f4d7d003b64fc96638b7b24676498d76fbc2439b89fa8c2239c
Tx public key: f408c096f72c6d89c06f19e70a153ff3f2a3cce6ffb97bb2402de3abc526aa12
| Timestamp: 1780976048 | Timestamp [UTC]: 2026-06-09 03:34:08 | Age [y:d:h:m:s]: 00:000:06:35:55 |
| Block: 7934 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 489 | RingCT/type: yes/0 |
| Extra: 01f408c096f72c6d89c06f19e70a153ff3f2a3cce6ffb97bb2402de3abc526aa12020900000002e49593ff00 | ||
1 output(s) for total of 34.656004412384 HMNY
| stealth address | amount | amount idx | tag |
| 00: ad6bb21d171449399dbd65a114fb4f6004123143f60e620448d8594a68b18c58 | 34.656004412384 | 9840 of 0 | <57> |
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": 7994,
"vin": [ {
"gen": {
"height": 7934
}
}
],
"vout": [ {
"amount": 34656004412384,
"target": {
"tagged_key": {
"key": "ad6bb21d171449399dbd65a114fb4f6004123143f60e620448d8594a68b18c58",
"view_tag": "57"
}
}
}
],
"extra": [ 1, 244, 8, 192, 150, 247, 44, 109, 137, 192, 111, 25, 231, 10, 21, 63, 243, 242, 163, 204, 230, 255, 185, 123, 178, 64, 45, 227, 171, 197, 38, 170, 18, 2, 9, 0, 0, 0, 2, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}