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: abe66f61f57b8e21d370aedc2be7e041e7d60d2fcb85e1b8a4f5cf81da1e9375
Tx prefix hash: d474c0b5624b2853d15dc8634d9195684011b1fb9069a5e2eef412d4c8cf34bb
Tx public key: e9487efb5c50787ef7337660acb69edfc23900fde48b8abd38b2477f6e3f89c0
| Timestamp: 1779723077 | Timestamp [UTC]: 2026-05-25 15:31:17 | Age [y:d:h:m:s]: 00:014:12:19:41 |
| Block: 1793 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 6188 | RingCT/type: yes/0 |
| Extra: 01e9487efb5c50787ef7337660acb69edfc23900fde48b8abd38b2477f6e3f89c0020900000003ba6d17be00 | ||
1 output(s) for total of 35.064318177301 HMNY
| stealth address | amount | amount idx | tag |
| 00: 40ed06e3234de0b62a5e9e7c8212135e5b6b57214f2ad8020c854ae19bd5e0d4 | 35.064318177301 | 1982 of 0 | <07> |
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": 1853,
"vin": [ {
"gen": {
"height": 1793
}
}
],
"vout": [ {
"amount": 35064318177301,
"target": {
"tagged_key": {
"key": "40ed06e3234de0b62a5e9e7c8212135e5b6b57214f2ad8020c854ae19bd5e0d4",
"view_tag": "07"
}
}
}
],
"extra": [ 1, 233, 72, 126, 251, 92, 80, 120, 126, 247, 51, 118, 96, 172, 182, 158, 223, 194, 57, 0, 253, 228, 139, 138, 189, 56, 178, 71, 127, 110, 63, 137, 192, 2, 9, 0, 0, 0, 3, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}