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: 00648c4fbbd47034c6d2e189a8f29662991b33269aaea83aaf1ac358c2a2bf8a
Tx prefix hash: f6bcf9beef4626ad10a20f9a8028a06c83b8c8c37517673da77d0590b673f4e9
Tx public key: c53afa2830d3683894abf6e3a1579284437d9db87177fee3ca8b49c53ac34e90
| Timestamp: 1780750952 | Timestamp [UTC]: 2026-06-06 13:02:32 | Age [y:d:h:m:s]: 00:010:20:12:34 |
| Block: 6489 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2256 | RingCT/type: yes/0 |
| Extra: 01c53afa2830d3683894abf6e3a1579284437d9db87177fee3ca8b49c53ac34e90020900000001e49593ff00 | ||
1 output(s) for total of 34.751652315953 HMNY
| stealth address | amount | amount idx | tag |
| 00: e0dc64ec45ea898f968b99b70eed443766f676379271e41c873506fd3bde9b9b | 34.751652315953 | 7986 of 0 | <a2> |
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": 6549,
"vin": [ {
"gen": {
"height": 6489
}
}
],
"vout": [ {
"amount": 34751652315953,
"target": {
"tagged_key": {
"key": "e0dc64ec45ea898f968b99b70eed443766f676379271e41c873506fd3bde9b9b",
"view_tag": "a2"
}
}
}
],
"extra": [ 1, 197, 58, 250, 40, 48, 211, 104, 56, 148, 171, 246, 227, 161, 87, 146, 132, 67, 125, 157, 184, 113, 119, 254, 227, 202, 139, 73, 197, 58, 195, 78, 144, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}