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: 0074667ee5286924aa395a925aac2baa382c4fc98ee238fbacfba522c45ff2ef
Tx prefix hash: 080369e92380f673d8e90ae5fdc98872d2f46d93eb72833f7ca7bab8c9a94baa
Tx public key: 33c23af208f0bf158e8ee8b1d0f98d1ad90e539a47ad1292ffa2257f2ab7f2ca
| Timestamp: 1780995566 | Timestamp [UTC]: 2026-06-09 08:59:26 | Age [y:d:h:m:s]: 00:000:04:38:10 |
| Block: 8324 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 276 | RingCT/type: yes/0 |
| Extra: 0133c23af208f0bf158e8ee8b1d0f98d1ad90e539a47ad1292ffa2257f2ab7f2ca020900000002e49593ff00 | ||
1 output(s) for total of 34.639268151430 HMNY
| stealth address | amount | amount idx | tag |
| 00: 9a9809e1c5d3996a0ac3b6e4e456c9cf9b0e427b688d281d1173f5cf9c44e9db | 34.639268151430 | 10296 of 0 | <b1> |
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": 8384,
"vin": [ {
"gen": {
"height": 8324
}
}
],
"vout": [ {
"amount": 34639268151430,
"target": {
"tagged_key": {
"key": "9a9809e1c5d3996a0ac3b6e4e456c9cf9b0e427b688d281d1173f5cf9c44e9db",
"view_tag": "b1"
}
}
}
],
"extra": [ 1, 51, 194, 58, 242, 8, 240, 191, 21, 142, 142, 232, 177, 208, 249, 141, 26, 217, 14, 83, 154, 71, 173, 18, 146, 255, 162, 37, 127, 42, 183, 242, 202, 2, 9, 0, 0, 0, 2, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}