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: 5766052c1a1cc040a91ff6c74e4f527f61f3db4da5f9471d3960bb0491cb8443
Tx prefix hash: 70ec48f2431f7ebecbbb7c09bcae1612f48c219689f47d53bb7810ea3d41240e
Tx public key: 17b9a18e669c98d0195a2fa8c1c657b8cfc6d360c770635c8993f5967e4814dd
| Timestamp: 1780776356 | Timestamp [UTC]: 2026-06-06 20:05:56 | Age [y:d:h:m:s]: 00:002:03:12:57 |
| Block: 6722 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1164 | RingCT/type: yes/0 |
| Extra: 0117b9a18e669c98d0195a2fa8c1c657b8cfc6d360c770635c8993f5967e4814dd020900000004e49593ff00 | ||
1 output(s) for total of 34.736211673134 HMNY
| stealth address | amount | amount idx | tag |
| 00: fc976153d79400e46d1ce6e545d30989ff569e84fe5505fd8d15d9318048256a | 34.736211673134 | 8292 of 0 | <4c> |
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": 6782,
"vin": [ {
"gen": {
"height": 6722
}
}
],
"vout": [ {
"amount": 34736211673134,
"target": {
"tagged_key": {
"key": "fc976153d79400e46d1ce6e545d30989ff569e84fe5505fd8d15d9318048256a",
"view_tag": "4c"
}
}
}
],
"extra": [ 1, 23, 185, 161, 142, 102, 156, 152, 208, 25, 90, 47, 168, 193, 198, 87, 184, 207, 198, 211, 96, 199, 112, 99, 92, 137, 147, 245, 150, 126, 72, 20, 221, 2, 9, 0, 0, 0, 4, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}