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: 1cf671d33d0b4d170a9588a806c28250e643bc2a4124d88efe89473416d55ac0
Tx prefix hash: 5d0f120df2b103ea822ea1c874f44b334df9da30b56b18159dc903e8786a8ab5
Tx public key: 685540841b6c9ea104bd32f70727b0e32f70e74ef9f9ec8f73ee4c68960ab50f
| Timestamp: 1779638713 | Timestamp [UTC]: 2026-05-24 16:05:13 | Age [y:d:h:m:s]: 00:015:11:33:37 |
| Block: 1211 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 6736 | RingCT/type: yes/0 |
| Extra: 01685540841b6c9ea104bd32f70727b0e32f70e74ef9f9ec8f73ee4c68960ab50f020900000001ba6d17be00 | ||
1 output(s) for total of 35.103263916600 HMNY
| stealth address | amount | amount idx | tag |
| 00: 0a458025d7e9def546cd642acab43533ddeb8b5d2d1583d8d539755377bd9b7b | 35.103263916600 | 1355 of 0 | <a7> |
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": 1271,
"vin": [ {
"gen": {
"height": 1211
}
}
],
"vout": [ {
"amount": 35103263916600,
"target": {
"tagged_key": {
"key": "0a458025d7e9def546cd642acab43533ddeb8b5d2d1583d8d539755377bd9b7b",
"view_tag": "a7"
}
}
}
],
"extra": [ 1, 104, 85, 64, 132, 27, 108, 158, 161, 4, 189, 50, 247, 7, 39, 176, 227, 47, 112, 231, 78, 249, 249, 236, 143, 115, 238, 76, 104, 150, 10, 181, 15, 2, 9, 0, 0, 0, 1, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}