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: a73a1407eeb058a30adcb2bd44ab8777c5fa9acca69bca103359839f5e6a196c
Tx prefix hash: f8cf366a12f8fdd9ca188333359c0563e509ea951fae3bc9835c2d15c5489ad5
Tx public key: a6b4c55bc325f1aa660f7f07ad1331fb580cbf1327d1352f5b8fb9f92bf5453b
| Timestamp: 1779437513 | Timestamp [UTC]: 2026-05-22 08:11:53 | Age [y:d:h:m:s]: 00:017:17:24:04 |
| Block: 165 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 7721 | RingCT/type: yes/0 |
| Extra: 01a6b4c55bc325f1aa660f7f07ad1331fb580cbf1327d1352f5b8fb9f92bf5453b020900000001a662ed0300 | ||
1 output(s) for total of 35.173367945921 HMNY
| stealth address | amount | amount idx | tag |
| 00: 7000c1378f99505b4d8cfbd5c2043ca7bb3a9b263c06aa5988fe51a93c6c8ffb | 35.173367945921 | 161 of 0 | <15> |
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": 225,
"vin": [ {
"gen": {
"height": 165
}
}
],
"vout": [ {
"amount": 35173367945921,
"target": {
"tagged_key": {
"key": "7000c1378f99505b4d8cfbd5c2043ca7bb3a9b263c06aa5988fe51a93c6c8ffb",
"view_tag": "15"
}
}
}
],
"extra": [ 1, 166, 180, 197, 91, 195, 37, 241, 170, 102, 15, 127, 7, 173, 19, 49, 251, 88, 12, 191, 19, 39, 209, 53, 47, 91, 143, 185, 249, 43, 245, 69, 59, 2, 9, 0, 0, 0, 1, 166, 98, 237, 3, 0
],
"rct_signatures": {
"type": 0
}
}