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: 5f498ade62a9eb145ff39dfb38e0a0cac21d2d09a55a354572cd7e9fc27141e6
Tx prefix hash: 475f7355a3716d5e32110adb1633a342b3ea9bb5d1273c9eb8ce3d2923b47af8
Tx public key: 78ef957f6d9c9a8222a8e54c9132f2c48a558ec350a142dfab8910ae4f9c20e4
| Timestamp: 1779635631 | Timestamp [UTC]: 2026-05-24 15:13:51 | Age [y:d:h:m:s]: 00:015:11:26:45 |
| Block: 1082 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 6814 | RingCT/type: yes/0 |
| Extra: 0178ef957f6d9c9a8222a8e54c9132f2c48a558ec350a142dfab8910ae4f9c20e4020900000001ba6d17be00 | ||
1 output(s) for total of 35.111902074450 HMNY
| stealth address | amount | amount idx | tag |
| 00: 4f39c42132933cb1f02cd9c2fd87e0d81ef262d6acb86b22d00d9a855dec59b9 | 35.111902074450 | 1222 of 0 | <08> |
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": 1142,
"vin": [ {
"gen": {
"height": 1082
}
}
],
"vout": [ {
"amount": 35111902074450,
"target": {
"tagged_key": {
"key": "4f39c42132933cb1f02cd9c2fd87e0d81ef262d6acb86b22d00d9a855dec59b9",
"view_tag": "08"
}
}
}
],
"extra": [ 1, 120, 239, 149, 127, 109, 156, 154, 130, 34, 168, 229, 76, 145, 50, 242, 196, 138, 85, 142, 195, 80, 161, 66, 223, 171, 137, 16, 174, 79, 156, 32, 228, 2, 9, 0, 0, 0, 1, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}