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: ca69d703755e18fba11989e7f396788280c92833b8ad5e91f1dab05b2b844b70
Tx prefix hash: 77ec6b075853a00cd224f5807ac214261e04b1d6a394ec3ff02e16d8cc9ee00a
Tx public key: 4cbc2b80c69497436306b3bf8fd2e3a548784c0b35e5838f74a33ec6786eca00
| Timestamp: 1780890142 | Timestamp [UTC]: 2026-06-08 03:42:22 | Age [y:d:h:m:s]: 00:000:21:04:25 |
| Block: 7715 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 171 | RingCT/type: yes/0 |
| Extra: 014cbc2b80c69497436306b3bf8fd2e3a548784c0b35e5838f74a33ec6786eca000209000000054a728a4c00 | ||
1 output(s) for total of 34.670483587122 HMNY
| stealth address | amount | amount idx | tag |
| 00: fe1a333e45b5cbfc621c6d05709fcf41a92cde6df5f732f36ad6d2404958057d | 34.670483587122 | 9549 of 0 | <3f> |
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": 7775,
"vin": [ {
"gen": {
"height": 7715
}
}
],
"vout": [ {
"amount": 34670483587122,
"target": {
"tagged_key": {
"key": "fe1a333e45b5cbfc621c6d05709fcf41a92cde6df5f732f36ad6d2404958057d",
"view_tag": "3f"
}
}
}
],
"extra": [ 1, 76, 188, 43, 128, 198, 148, 151, 67, 99, 6, 179, 191, 143, 210, 227, 165, 72, 120, 76, 11, 53, 229, 131, 143, 116, 163, 62, 198, 120, 110, 202, 0, 2, 9, 0, 0, 0, 5, 74, 114, 138, 76, 0
],
"rct_signatures": {
"type": 0
}
}