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: 390d0e68314c676c4fe5a7f22f13dcd6d36d341adf775fee385043f2cd9fb743
Tx prefix hash: 96b3087041d5c42125e6c7ce36b9f55bef44eed535d8f438e1f0be50325ed937
Tx public key: 791f52a9e056f97ad3629b63cf074773fb311c6f162f05b8f787ee54f399cb87
| Timestamp: 1780761931 | Timestamp [UTC]: 2026-06-06 16:05:31 | Age [y:d:h:m:s]: 00:002:08:41:16 |
| Block: 6579 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1307 | RingCT/type: yes/0 |
| Extra: 01791f52a9e056f97ad3629b63cf074773fb311c6f162f05b8f787ee54f399cb87020900000001e49593ff00 | ||
1 output(s) for total of 34.745687305771 HMNY
| stealth address | amount | amount idx | tag |
| 00: a9c64e4bef30b3f789a8df2ebd77a9352a859c4859edaf66c214fa4e4b6cfa72 | 34.745687305771 | 8103 of 0 | <05> |
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": 6639,
"vin": [ {
"gen": {
"height": 6579
}
}
],
"vout": [ {
"amount": 34745687305771,
"target": {
"tagged_key": {
"key": "a9c64e4bef30b3f789a8df2ebd77a9352a859c4859edaf66c214fa4e4b6cfa72",
"view_tag": "05"
}
}
}
],
"extra": [ 1, 121, 31, 82, 169, 224, 86, 249, 122, 211, 98, 155, 99, 207, 7, 71, 115, 251, 49, 28, 111, 22, 47, 5, 184, 247, 135, 238, 84, 243, 153, 203, 135, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}