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: bb50ec33dc3ad70cca77ac34e4772f496255d08b297e7a269ef02ffbf27880c6
Tx prefix hash: 5da6773763d014751c984c25ceec23f0c8474f763645e55b727bb9f12bc5b642
Tx public key: c07a55c0b4cd357bdf463b039a5950477528895eb2f2c6f4784b50972881ad1d
| Timestamp: 1780693090 | Timestamp [UTC]: 2026-06-05 20:58:10 | Age [y:d:h:m:s]: 00:003:04:37:47 |
| Block: 5842 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2044 | RingCT/type: yes/0 |
| Extra: 01c07a55c0b4cd357bdf463b039a5950477528895eb2f2c6f4784b50972881ad1d020900000001e49593ff00 | ||
1 output(s) for total of 34.794564264470 HMNY
| stealth address | amount | amount idx | tag |
| 00: 637d86f8cc132e3d29601a69a5b890d0413a722c884be8a94a5c14d8a9a36ee8 | 34.794564264470 | 7299 of 0 | <63> |
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": 5902,
"vin": [ {
"gen": {
"height": 5842
}
}
],
"vout": [ {
"amount": 34794564264470,
"target": {
"tagged_key": {
"key": "637d86f8cc132e3d29601a69a5b890d0413a722c884be8a94a5c14d8a9a36ee8",
"view_tag": "63"
}
}
}
],
"extra": [ 1, 192, 122, 85, 192, 180, 205, 53, 123, 223, 70, 59, 3, 154, 89, 80, 71, 117, 40, 137, 94, 178, 242, 198, 244, 120, 75, 80, 151, 40, 129, 173, 29, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}