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: aaca2da06035f4ed988ce2091263a1a87c8e09237af7fa56ead3d201480bf9bd
Tx prefix hash: 5416ef25359d32f56524d1e913a009691f7695101e66c79f443041887391bd8e
Tx public key: 3d60719ab01ba6d0b61c23c43723900faae02d62b4c6a6b085af73a50a3e34d6
| Timestamp: 1779718256 | Timestamp [UTC]: 2026-05-25 14:10:56 | Age [y:d:h:m:s]: 00:014:11:25:01 |
| Block: 1699 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 6187 | RingCT/type: yes/0 |
| Extra: 013d60719ab01ba6d0b61c23c43723900faae02d62b4c6a6b085af73a50a3e34d6020900000005ba6d17be00 | ||
1 output(s) for total of 35.070605455564 HMNY
| stealth address | amount | amount idx | tag |
| 00: 2430ad5ba24f196dbfad188f25b62b77d7b513492f60bdf596fee00aec07225e | 35.070605455564 | 1870 of 0 | <86> |
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": 1759,
"vin": [ {
"gen": {
"height": 1699
}
}
],
"vout": [ {
"amount": 35070605455564,
"target": {
"tagged_key": {
"key": "2430ad5ba24f196dbfad188f25b62b77d7b513492f60bdf596fee00aec07225e",
"view_tag": "86"
}
}
}
],
"extra": [ 1, 61, 96, 113, 154, 176, 27, 166, 208, 182, 28, 35, 196, 55, 35, 144, 15, 170, 224, 45, 98, 180, 198, 166, 176, 133, 175, 115, 165, 10, 62, 52, 214, 2, 9, 0, 0, 0, 5, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}