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: 3a7f8bca36e915ea112b0c20d7155053f162d403fd776ad6e4a5b98e1e8c6807
Tx prefix hash: c33f6ffd0d2c9809793a31656a80baa9cccf43345e9b2496e43611f9573046ef
Tx public key: e8183308c43addaff8762e01cd23c5ea9435f33d01bf0a3b7cb6f7b021038d99
| Timestamp: 1779465310 | Timestamp [UTC]: 2026-05-22 15:55:10 | Age [y:d:h:m:s]: 00:017:09:40:47 |
| Block: 498 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 7388 | RingCT/type: yes/0 |
| Extra: 01e8183308c43addaff8762e01cd23c5ea9435f33d01bf0a3b7cb6f7b021038d9902090000000293369e7d00 | ||
1 output(s) for total of 35.151034755341 HMNY
| stealth address | amount | amount idx | tag |
| 00: 064dc249efd926263cb4c030501fc500f59468271e169f8ed7e9353eb4299118 | 35.151034755341 | 502 of 0 | <10> |
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": 558,
"vin": [ {
"gen": {
"height": 498
}
}
],
"vout": [ {
"amount": 35151034755341,
"target": {
"tagged_key": {
"key": "064dc249efd926263cb4c030501fc500f59468271e169f8ed7e9353eb4299118",
"view_tag": "10"
}
}
}
],
"extra": [ 1, 232, 24, 51, 8, 196, 58, 221, 175, 248, 118, 46, 1, 205, 35, 197, 234, 148, 53, 243, 61, 1, 191, 10, 59, 124, 182, 247, 176, 33, 3, 141, 153, 2, 9, 0, 0, 0, 2, 147, 54, 158, 125, 0
],
"rct_signatures": {
"type": 0
}
}