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: e6e9280d6e0edce12e303c2294d7e33ed694365ef3b37e4b4cfa3352c02be94f
Tx prefix hash: a902ad9b399ad40919427867cb6b925e585a01619c1d382b69406f7ae031b5f2
Tx public key: 3bc867d6edee31bce4858618a797469eda1b3a487db9424f8ac8b02589d8f2a9
| Timestamp: 1779641501 | Timestamp [UTC]: 2026-05-24 16:51:41 | Age [y:d:h:m:s]: 00:015:07:55:06 |
| Block: 1338 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0820 kB |
| Tx version: 2 | No of confirmations: 6548 | RingCT/type: yes/0 |
| Extra: 013bc867d6edee31bce4858618a797469eda1b3a487db9424f8ac8b02589d8f2a9 | ||
1 output(s) for total of 35.094761759656 HMNY
| stealth address | amount | amount idx | tag |
| 00: caee55740075447b4f098e08593b556b5be8ca5fcc48befb53cd62d604878fdc | 35.094761759656 | 1488 of 0 | <a4> |
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": 1398,
"vin": [ {
"gen": {
"height": 1338
}
}
],
"vout": [ {
"amount": 35094761759656,
"target": {
"tagged_key": {
"key": "caee55740075447b4f098e08593b556b5be8ca5fcc48befb53cd62d604878fdc",
"view_tag": "a4"
}
}
}
],
"extra": [ 1, 59, 200, 103, 214, 237, 238, 49, 188, 228, 133, 134, 24, 167, 151, 70, 158, 218, 27, 58, 72, 125, 185, 66, 79, 138, 200, 176, 37, 137, 216, 242, 169
],
"rct_signatures": {
"type": 0
}
}