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: db7c42518d4aa581abed300fa327d6a2c6ea179d7f2cf9e91a7722d003a0dfe9
Tx prefix hash: 3ef707b66d6a60e59f6a87d0daddb3b5c372fdc6c2b0e94483f137c5b0b95fdc
Tx public key: bd51556c79ad4b1217a216500f4d729dfaff24d4d79960a10adfad573ca3fe09
| Timestamp: 1781000532 | Timestamp [UTC]: 2026-06-09 10:22:12 | Age [y:d:h:m:s]: 00:000:06:46:51 |
| Block: 8435 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 297 | RingCT/type: yes/0 |
| Extra: 01bd51556c79ad4b1217a216500f4d729dfaff24d4d79960a10adfad573ca3fe09020900000001e49593ff00 | ||
1 output(s) for total of 34.622903556221 HMNY
| stealth address | amount | amount idx | tag |
| 00: caf7a7c8fa6f4f2602b3ac330db996cf2c36f4e6663336a2b56640a7a774cc6f | 34.622903556221 | 10425 of 0 | <bd> |
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": 8495,
"vin": [ {
"gen": {
"height": 8435
}
}
],
"vout": [ {
"amount": 34622903556221,
"target": {
"tagged_key": {
"key": "caf7a7c8fa6f4f2602b3ac330db996cf2c36f4e6663336a2b56640a7a774cc6f",
"view_tag": "bd"
}
}
}
],
"extra": [ 1, 189, 81, 85, 108, 121, 173, 75, 18, 23, 162, 22, 80, 15, 77, 114, 157, 250, 255, 36, 212, 215, 153, 96, 161, 10, 223, 173, 87, 60, 163, 254, 9, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}