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: d336c0dd0383f805c5d7d8adf35a5d577fd63cbf0f039bb776569cb5dd5a3f29
Tx prefix hash: 900f9c91c8eda1357a6c0100cad79ece0c95a788d1272ea2fc5f0a6bc41451bb
Tx public key: b9c7cd971ad322b06d42bf1de2cefc60e0af271e52cec7835a0e271d58afc8a6
| Timestamp: 1780803137 | Timestamp [UTC]: 2026-06-07 03:32:17 | Age [y:d:h:m:s]: 00:001:21:14:30 |
| Block: 6879 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1007 | RingCT/type: yes/0 |
| Extra: 01b9c7cd971ad322b06d42bf1de2cefc60e0af271e52cec7835a0e271d58afc8a6020900000001e49593ff00 | ||
1 output(s) for total of 34.725811332167 HMNY
| stealth address | amount | amount idx | tag |
| 00: 97b15ae12e5f03125227f43cc2876ceace10b77fabe69508b16ca3dedc358ea4 | 34.725811332167 | 8491 of 0 | <fc> |
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": 6939,
"vin": [ {
"gen": {
"height": 6879
}
}
],
"vout": [ {
"amount": 34725811332167,
"target": {
"tagged_key": {
"key": "97b15ae12e5f03125227f43cc2876ceace10b77fabe69508b16ca3dedc358ea4",
"view_tag": "fc"
}
}
}
],
"extra": [ 1, 185, 199, 205, 151, 26, 211, 34, 176, 109, 66, 191, 29, 226, 206, 252, 96, 224, 175, 39, 30, 82, 206, 199, 131, 90, 14, 39, 29, 88, 175, 200, 166, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}