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: 33be78f54fbe4f60c7f86cb27dd5e37067607b3552cb769945cfac387d4c5889
Tx prefix hash: c0729b5972b9bf2f052756fa2151d4ee2b32eb63ae4bff03f5e9980548dc9aee
Tx public key: a405432f742358949ef7161cb71222d175a2d3850f501e48e2225877cf5edd09
| Timestamp: 1779637182 | Timestamp [UTC]: 2026-05-24 15:39:42 | Age [y:d:h:m:s]: 00:015:11:00:54 |
| Block: 1148 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 6749 | RingCT/type: yes/0 |
| Extra: 01a405432f742358949ef7161cb71222d175a2d3850f501e48e2225877cf5edd09020900000001ba6d17be00 | ||
1 output(s) for total of 35.107482286297 HMNY
| stealth address | amount | amount idx | tag |
| 00: 557a75f91aa193835ef85ed7cb20c3d0378d9e89d12b5bcde9fb7552b3eba17e | 35.107482286297 | 1290 of 0 | <9b> |
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": 1208,
"vin": [ {
"gen": {
"height": 1148
}
}
],
"vout": [ {
"amount": 35107482286297,
"target": {
"tagged_key": {
"key": "557a75f91aa193835ef85ed7cb20c3d0378d9e89d12b5bcde9fb7552b3eba17e",
"view_tag": "9b"
}
}
}
],
"extra": [ 1, 164, 5, 67, 47, 116, 35, 88, 148, 158, 247, 22, 28, 183, 18, 34, 209, 117, 162, 211, 133, 15, 80, 30, 72, 226, 34, 88, 119, 207, 94, 221, 9, 2, 9, 0, 0, 0, 1, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}