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: a13817d73187f9fdda761d82b0a081c184e1cdacd7af64e3ea0cfd54d1a0ad3e
Tx prefix hash: 02e06dae52fcc48546fb6d442ff798119a7187be9a009efb13edc8c6795d9211
Tx public key: ca828a997f2a99e36c8f8c4e344c23e26251f9ea8571e38c502fe5a1cd741ec5
| Timestamp: 1780120225 | Timestamp [UTC]: 2026-05-30 05:50:25 | Age [y:d:h:m:s]: 00:009:19:45:32 |
| Block: 4892 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2994 | RingCT/type: yes/0 |
| Extra: 01ca828a997f2a99e36c8f8c4e344c23e26251f9ea8571e38c502fe5a1cd741ec502090000000126697be300 | ||
1 output(s) for total of 34.857668575649 HMNY
| stealth address | amount | amount idx | tag |
| 00: 1170cd0ae6a019ed7bdd5a8dcde87492158fb702c842e6f6e93b2c5ecce87536 | 34.857668575649 | 6194 of 0 | <b0> |
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": 4952,
"vin": [ {
"gen": {
"height": 4892
}
}
],
"vout": [ {
"amount": 34857668575649,
"target": {
"tagged_key": {
"key": "1170cd0ae6a019ed7bdd5a8dcde87492158fb702c842e6f6e93b2c5ecce87536",
"view_tag": "b0"
}
}
}
],
"extra": [ 1, 202, 130, 138, 153, 127, 42, 153, 227, 108, 143, 140, 78, 52, 76, 35, 226, 98, 81, 249, 234, 133, 113, 227, 140, 80, 47, 229, 161, 205, 116, 30, 197, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}