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: 625e67738aa0aaad820da928d37730ac8377d84026250ce4c062a69f2018e387
Tx prefix hash: 0392b14c359d85dfc095b6e584c9f758c4350297b6882100718895e50afe2ab7
Tx public key: 9975845c51c03ed12425a038813ac8ffbfc56404736caa90a551bab932bd13b9
| Timestamp: 1780980715 | Timestamp [UTC]: 2026-06-09 04:51:55 | Age [y:d:h:m:s]: 00:000:06:34:53 |
| Block: 8024 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 492 | RingCT/type: yes/0 |
| Extra: 019975845c51c03ed12425a038813ac8ffbfc56404736caa90a551bab932bd13b9020900000001e49593ff00 | ||
1 output(s) for total of 34.650055819860 HMNY
| stealth address | amount | amount idx | tag |
| 00: 9482455230f1d458d083a8bd299c1280bc187d516c20d06b86f4d395b8c1b2cc | 34.650055819860 | 9948 of 0 | <d4> |
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": 8084,
"vin": [ {
"gen": {
"height": 8024
}
}
],
"vout": [ {
"amount": 34650055819860,
"target": {
"tagged_key": {
"key": "9482455230f1d458d083a8bd299c1280bc187d516c20d06b86f4d395b8c1b2cc",
"view_tag": "d4"
}
}
}
],
"extra": [ 1, 153, 117, 132, 92, 81, 192, 62, 209, 36, 37, 160, 56, 129, 58, 200, 255, 191, 197, 100, 4, 115, 108, 170, 144, 165, 81, 186, 185, 50, 189, 19, 185, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}