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: 49edc0001b8e1ef5c34e7ed15b8301fc478b4e0909654ea4c8a2f0e1a75a5c71
Tx prefix hash: 399a1f338b9cadf21ceeef424c7e3cb4dc9ce071f1a727629451b3f784fcffdb
Tx public key: 934c94ea291d013905072ea9c289cd4b84db45ba29fca8ccc5c53c4682c79d3b
| Timestamp: 1780994806 | Timestamp [UTC]: 2026-06-09 08:46:46 | Age [y:d:h:m:s]: 00:000:08:22:17 |
| Block: 8310 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 420 | RingCT/type: yes/0 |
| Extra: 01934c94ea291d013905072ea9c289cd4b84db45ba29fca8ccc5c53c4682c79d3b020900000001e49593ff00 | ||
1 output(s) for total of 34.631159291685 HMNY
| stealth address | amount | amount idx | tag |
| 00: 3964f4c2e2512b172939149bae98445fa2e24c15263925646b1a7ddaf3b4757b | 34.631159291685 | 10280 of 0 | <61> |
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": 8370,
"vin": [ {
"gen": {
"height": 8310
}
}
],
"vout": [ {
"amount": 34631159291685,
"target": {
"tagged_key": {
"key": "3964f4c2e2512b172939149bae98445fa2e24c15263925646b1a7ddaf3b4757b",
"view_tag": "61"
}
}
}
],
"extra": [ 1, 147, 76, 148, 234, 41, 29, 1, 57, 5, 7, 46, 169, 194, 137, 205, 75, 132, 219, 69, 186, 41, 252, 168, 204, 197, 197, 60, 70, 130, 199, 157, 59, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}