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: 6039aa2def09b200a8d137bdbd2e1605679f982f371dd52cbf087c96d2b11bd4
Tx prefix hash: 21c6469db3d1c032df4cd96804cf534bedfb6983926d62223ebd597c3237df5d
Tx public key: a09bbec5dfa7888cbabafbaf0708f085d7bdd1aa1de4f2efbb25efce4dbc9c11
| Timestamp: 1780323253 | Timestamp [UTC]: 2026-06-01 14:14:13 | Age [y:d:h:m:s]: 00:008:02:54:50 |
| Block: 5088 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3646 | RingCT/type: yes/0 |
| Extra: 01a09bbec5dfa7888cbabafbaf0708f085d7bdd1aa1de4f2efbb25efce4dbc9c1102090000000226697be300 | ||
1 output(s) for total of 34.844639796323 HMNY
| stealth address | amount | amount idx | tag |
| 00: 7c3470ad2c16ee28b29520adec9e0fe5bac76012039bd4117dbaec9a9480db31 | 34.844639796323 | 6463 of 0 | <e9> |
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": 5148,
"vin": [ {
"gen": {
"height": 5088
}
}
],
"vout": [ {
"amount": 34844639796323,
"target": {
"tagged_key": {
"key": "7c3470ad2c16ee28b29520adec9e0fe5bac76012039bd4117dbaec9a9480db31",
"view_tag": "e9"
}
}
}
],
"extra": [ 1, 160, 155, 190, 197, 223, 167, 136, 140, 186, 186, 251, 175, 7, 8, 240, 133, 215, 189, 209, 170, 29, 228, 242, 239, 187, 37, 239, 206, 77, 188, 156, 17, 2, 9, 0, 0, 0, 2, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}