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: 560cf6061c5e2c47240cafe638537ce07fee8bd0956f7511f427998fb9d6d629
Tx prefix hash: a0f322c344a81129be5ae44c392ecbe9b5eb79bfb78128946dea27d650cecc38
Tx public key: 9c363e2feb36f437b58a6020d6e84417a37c8a7b2d567253faf14c9dd9e0bf02
| Timestamp: 1780996809 | Timestamp [UTC]: 2026-06-09 09:20:09 | Age [y:d:h:m:s]: 00:000:05:28:46 |
| Block: 8361 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 281 | RingCT/type: yes/0 |
| Extra: 019c363e2feb36f437b58a6020d6e84417a37c8a7b2d567253faf14c9dd9e0bf02020900000001e49593ff00 | ||
1 output(s) for total of 34.627790713904 HMNY
| stealth address | amount | amount idx | tag |
| 00: c145f918b6d5b4f77be939285732059a83884cb26436353d4c379ab408dc80a8 | 34.627790713904 | 10339 of 0 | <3a> |
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": 8421,
"vin": [ {
"gen": {
"height": 8361
}
}
],
"vout": [ {
"amount": 34627790713904,
"target": {
"tagged_key": {
"key": "c145f918b6d5b4f77be939285732059a83884cb26436353d4c379ab408dc80a8",
"view_tag": "3a"
}
}
}
],
"extra": [ 1, 156, 54, 62, 47, 235, 54, 244, 55, 181, 138, 96, 32, 214, 232, 68, 23, 163, 124, 138, 123, 45, 86, 114, 83, 250, 241, 76, 157, 217, 224, 191, 2, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}