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: a00bf084d100262888935cdccd86313f4099e5ed948a08b032c033622e14135a
Tx prefix hash: 2b277e8640829de53d999df77aaf0285c8255ef1d7da4c428a77925b2ff5c92a
Tx public key: 1f53b5faec4f60b7fed7078b7479805f7fb04ab3c913aab5300dea70950d3b09
| Timestamp: 1779639041 | Timestamp [UTC]: 2026-05-24 16:10:41 | Age [y:d:h:m:s]: 00:015:08:36:06 |
| Block: 1233 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 6653 | RingCT/type: yes/0 |
| Extra: 011f53b5faec4f60b7fed7078b7479805f7fb04ab3c913aab5300dea70950d3b09020900000001ba6d17be00 | ||
1 output(s) for total of 35.101790954526 HMNY
| stealth address | amount | amount idx | tag |
| 00: 240b67bcba708e07e927076fdd9650b1c97ad80537bcde91c9a59ae027700d50 | 35.101790954526 | 1379 of 0 | <67> |
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": 1293,
"vin": [ {
"gen": {
"height": 1233
}
}
],
"vout": [ {
"amount": 35101790954526,
"target": {
"tagged_key": {
"key": "240b67bcba708e07e927076fdd9650b1c97ad80537bcde91c9a59ae027700d50",
"view_tag": "67"
}
}
}
],
"extra": [ 1, 31, 83, 181, 250, 236, 79, 96, 183, 254, 215, 7, 139, 116, 121, 128, 95, 127, 176, 74, 179, 201, 19, 170, 181, 48, 13, 234, 112, 149, 13, 59, 9, 2, 9, 0, 0, 0, 1, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}