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: ac54ca2882818109277875c43e4f828d407cd9f12749cc3368f6b8e85361e4e7
Tx prefix hash: 8b3f3e1d220ab2fb7c66825d80c75e88e2ec60e98ffcc6cfe8cc7f4d58923110
Tx public key: 4305f3686ded1c4a16c3f75dfe47db024ea01685a7bff8f5b1329a1e5396ed26
| Timestamp: 1781005368 | Timestamp [UTC]: 2026-06-09 11:42:48 | Age [y:d:h:m:s]: 00:006:06:31:54 |
| Block: 8529 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 216 | RingCT/type: yes/0 |
| Extra: 014305f3686ded1c4a16c3f75dfe47db024ea01685a7bff8f5b1329a1e5396ed26020900000002e49593ff00 | ||
1 output(s) for total of 34.616696539659 HMNY
| stealth address | amount | amount idx | tag |
| 00: 678ced73f403a00680eb6b3006674df50eccbe2a48ece6982d616498dc187513 | 34.616696539659 | 10535 of 0 | <3a> |
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": 8589,
"vin": [ {
"gen": {
"height": 8529
}
}
],
"vout": [ {
"amount": 34616696539659,
"target": {
"tagged_key": {
"key": "678ced73f403a00680eb6b3006674df50eccbe2a48ece6982d616498dc187513",
"view_tag": "3a"
}
}
}
],
"extra": [ 1, 67, 5, 243, 104, 109, 237, 28, 74, 22, 195, 247, 93, 254, 71, 219, 2, 78, 160, 22, 133, 167, 191, 248, 245, 177, 50, 154, 30, 83, 150, 237, 38, 2, 9, 0, 0, 0, 2, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}