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: 1fd49120944c82d8349a0fb2d222ddb41c1d2869ef1a74b4e1c18d04f3ed5047
Tx prefix hash: 7606e8223734cf049ae4e04093bddebc272e7046c9601246cc2f754937fa2bce
Tx public key: cbb009f202765419b63f6e667f6033a140367d317fe57b211c95158eefecaef4
| Timestamp: 1780689637 | Timestamp [UTC]: 2026-06-05 20:00:37 | Age [y:d:h:m:s]: 00:003:04:46:10 |
| Block: 5608 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2278 | RingCT/type: yes/0 |
| Extra: 01cbb009f202765419b63f6e667f6033a140367d317fe57b211c95158eefecaef4020900000001e49593ff00 | ||
1 output(s) for total of 34.810097240673 HMNY
| stealth address | amount | amount idx | tag |
| 00: f57b6036c459623da5408551cbe4b84c72170db1af6295f4b81b0368795a7b52 | 34.810097240673 | 7055 of 0 | <51> |
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": 5668,
"vin": [ {
"gen": {
"height": 5608
}
}
],
"vout": [ {
"amount": 34810097240673,
"target": {
"tagged_key": {
"key": "f57b6036c459623da5408551cbe4b84c72170db1af6295f4b81b0368795a7b52",
"view_tag": "51"
}
}
}
],
"extra": [ 1, 203, 176, 9, 242, 2, 118, 84, 25, 182, 63, 110, 102, 127, 96, 51, 161, 64, 54, 125, 49, 127, 229, 123, 33, 28, 149, 21, 142, 239, 236, 174, 244, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}