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: 1fb70b5e73002f9b9080bbeb7b17155b4357ebf13708f60a9809321d14d0d1b0
Tx prefix hash: d0954d52a7f7f72af3da62fe0fdc52992c3e55ea84e05380c7c0f73941fe469d
Tx public key: 9659d0932d413335df311b33cd78a438707aae261b06105a5a7c1a184cee4e03
| Timestamp: 1780893008 | Timestamp [UTC]: 2026-06-08 04:30:08 | Age [y:d:h:m:s]: 00:000:20:16:39 |
| Block: 7740 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 146 | RingCT/type: yes/0 |
| Extra: 019659d0932d413335df311b33cd78a438707aae261b06105a5a7c1a184cee4e030209000000014a728a4c00 | ||
1 output(s) for total of 34.673848807474 HMNY
| stealth address | amount | amount idx | tag |
| 00: 18a5e98ea125b5b1e3dea3ee3e68997068503f68b8b7ec8bc5ad4d0534f60987 | 34.673848807474 | 9582 of 0 | <17> |
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": 7800,
"vin": [ {
"gen": {
"height": 7740
}
}
],
"vout": [ {
"amount": 34673848807474,
"target": {
"tagged_key": {
"key": "18a5e98ea125b5b1e3dea3ee3e68997068503f68b8b7ec8bc5ad4d0534f60987",
"view_tag": "17"
}
}
}
],
"extra": [ 1, 150, 89, 208, 147, 45, 65, 51, 53, 223, 49, 27, 51, 205, 120, 164, 56, 112, 122, 174, 38, 27, 6, 16, 90, 90, 124, 26, 24, 76, 238, 78, 3, 2, 9, 0, 0, 0, 1, 74, 114, 138, 76, 0
],
"rct_signatures": {
"type": 0
}
}