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: 78f3eabafcd252811b751ce61003dc2f013451890d92d2a2134b8ec78e47d360
Tx prefix hash: e6f7fa4e9777488c992780f1373d456647a7ae42365c4399b2a2c89898a02491
Tx public key: dcf0905182fe42e64b6bfec895dd7ef52cce9460b6c9817b96edaf80ce4547c5
| Timestamp: 1779634522 | Timestamp [UTC]: 2026-05-24 14:55:22 | Age [y:d:h:m:s]: 00:023:17:26:57 |
| Block: 1038 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0820 kB |
| Tx version: 2 | No of confirmations: 7707 | RingCT/type: yes/0 |
| Extra: 01dcf0905182fe42e64b6bfec895dd7ef52cce9460b6c9817b96edaf80ce4547c5 | ||
1 output(s) for total of 35.114848909003 HMNY
| stealth address | amount | amount idx | tag |
| 00: e49f9c86b9521657e34304171365cd9299b0289e3cabe1eb3874855074a491a8 | 35.114848909003 | 1176 of 0 | <a6> |
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": 1098,
"vin": [ {
"gen": {
"height": 1038
}
}
],
"vout": [ {
"amount": 35114848909003,
"target": {
"tagged_key": {
"key": "e49f9c86b9521657e34304171365cd9299b0289e3cabe1eb3874855074a491a8",
"view_tag": "a6"
}
}
}
],
"extra": [ 1, 220, 240, 144, 81, 130, 254, 66, 230, 75, 107, 254, 200, 149, 221, 126, 245, 44, 206, 148, 96, 182, 201, 129, 123, 150, 237, 175, 128, 206, 69, 71, 197
],
"rct_signatures": {
"type": 0
}
}