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: d1cc7c8679471ce7dfef3c3547f1f89fb50cb99804ce60995a9f096e0b164556
Tx prefix hash: 416eea2dbb905ced73718e40570142c48c2ba028af9a271b490026fce947cebf
Tx public key: 2fcad43710ecf65ec59e77584cdd063fe6e53fc5e1f884239eb7a3e24dc76075
| Timestamp: 1781007935 | Timestamp [UTC]: 2026-06-09 12:25:35 | Age [y:d:h:m:s]: 00:000:04:26:21 |
| Block: 8570 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 154 | RingCT/type: yes/0 |
| Extra: 012fcad43710ecf65ec59e77584cdd063fe6e53fc5e1f884239eb7a3e24dc7607502090000000be49593ff00 | ||
1 output(s) for total of 34.613989572461 HMNY
| stealth address | amount | amount idx | tag |
| 00: a7c5bea1c9ef6849bc433208721197c4d80f190716d634dcd277b97f937f0f34 | 34.613989572461 | 10584 of 0 | <d7> |
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": 8630,
"vin": [ {
"gen": {
"height": 8570
}
}
],
"vout": [ {
"amount": 34613989572461,
"target": {
"tagged_key": {
"key": "a7c5bea1c9ef6849bc433208721197c4d80f190716d634dcd277b97f937f0f34",
"view_tag": "d7"
}
}
}
],
"extra": [ 1, 47, 202, 212, 55, 16, 236, 246, 94, 197, 158, 119, 88, 76, 221, 6, 63, 230, 229, 63, 197, 225, 248, 132, 35, 158, 183, 163, 226, 77, 199, 96, 117, 2, 9, 0, 0, 0, 11, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}