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: 569ca7d677eff1a7d2d2d09742eae8f1151d4670f7a0f28137f360b2cfaf0da3
Tx prefix hash: 29c0e655a505d491ea7f678098166ae87c22d68f86c5f37f28b29894138c6037
Tx public key: 9425625a74232e1338888e1981f70889d364df938c1662078c8858428f309f9a
| Timestamp: 1780774194 | Timestamp [UTC]: 2026-06-06 19:29:54 | Age [y:d:h:m:s]: 00:006:15:51:11 |
| Block: 6698 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2047 | RingCT/type: yes/0 |
| Extra: 019425625a74232e1338888e1981f70889d364df938c1662078c8858428f309f9a020900000001e49593ff00 | ||
1 output(s) for total of 34.744422208626 HMNY
| stealth address | amount | amount idx | tag |
| 00: afe05bd6315bc82cfd9eb8c582df6c4e01b7a0dc78380d31f5af8284c893aecb | 34.744422208626 | 8260 of 0 | <66> |
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": 6758,
"vin": [ {
"gen": {
"height": 6698
}
}
],
"vout": [ {
"amount": 34744422208626,
"target": {
"tagged_key": {
"key": "afe05bd6315bc82cfd9eb8c582df6c4e01b7a0dc78380d31f5af8284c893aecb",
"view_tag": "66"
}
}
}
],
"extra": [ 1, 148, 37, 98, 90, 116, 35, 46, 19, 56, 136, 142, 25, 129, 247, 8, 137, 211, 100, 223, 147, 140, 22, 98, 7, 140, 136, 88, 66, 143, 48, 159, 154, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}