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: 335d4da064f3851750ba5db4f9dc524763b66a5d8740e15570e0597a62a92e9f
Tx prefix hash: e9f7bd0ffffc279b0f28cf306867a9816ec4a0268a144d80016845ae4dae7e24
Tx public key: 5ddf70c7959d04cdffbf6610ace31886c9b3ff8ebbd1b1d55e2c52642f213054
| Timestamp: 1779637549 | Timestamp [UTC]: 2026-05-24 15:45:49 | Age [y:d:h:m:s]: 00:015:11:03:59 |
| Block: 1163 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 6757 | RingCT/type: yes/0 |
| Extra: 015ddf70c7959d04cdffbf6610ace31886c9b3ff8ebbd1b1d55e2c52642f213054020900000001ba6d17be00 | ||
1 output(s) for total of 35.106477866583 HMNY
| stealth address | amount | amount idx | tag |
| 00: dd97bc99d99e14c67501f8b13aa2a54bf692573333ad245d1761508d39ba9df6 | 35.106477866583 | 1305 of 0 | <67> |
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": 1223,
"vin": [ {
"gen": {
"height": 1163
}
}
],
"vout": [ {
"amount": 35106477866583,
"target": {
"tagged_key": {
"key": "dd97bc99d99e14c67501f8b13aa2a54bf692573333ad245d1761508d39ba9df6",
"view_tag": "67"
}
}
}
],
"extra": [ 1, 93, 223, 112, 199, 149, 157, 4, 205, 255, 191, 102, 16, 172, 227, 24, 134, 201, 179, 255, 142, 187, 209, 177, 213, 94, 44, 82, 100, 47, 33, 48, 84, 2, 9, 0, 0, 0, 1, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}