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: 6d41ff366241f96c95ba7558a48905407504af2e234677ec0cc2bdb463f95e0d
Tx prefix hash: b9fbbba546e6508005a0ce0b121840a93e39e7b5c46ecdc6a897f61bc992585f
Tx public key: 7b44a90d69b2dcecea1a9bc2600536d4649aba49174a3f27167ef4bcbc3e7878
| Timestamp: 1779916583 | Timestamp [UTC]: 2026-05-27 21:16:23 | Age [y:d:h:m:s]: 00:012:04:19:34 |
| Block: 3313 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4573 | RingCT/type: yes/0 |
| Extra: 017b44a90d69b2dcecea1a9bc2600536d4649aba49174a3f27167ef4bcbc3e787802090000000226697be300 | ||
1 output(s) for total of 34.962807882800 HMNY
| stealth address | amount | amount idx | tag |
| 00: 8f6a5c7ab3ef5f084a62f719ca839a8768ecc4f2e429736a071d3853bbff5581 | 34.962807882800 | 3979 of 0 | <18> |
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": 3373,
"vin": [ {
"gen": {
"height": 3313
}
}
],
"vout": [ {
"amount": 34962807882800,
"target": {
"tagged_key": {
"key": "8f6a5c7ab3ef5f084a62f719ca839a8768ecc4f2e429736a071d3853bbff5581",
"view_tag": "18"
}
}
}
],
"extra": [ 1, 123, 68, 169, 13, 105, 178, 220, 236, 234, 26, 155, 194, 96, 5, 54, 212, 100, 154, 186, 73, 23, 74, 63, 39, 22, 126, 244, 188, 188, 62, 120, 120, 2, 9, 0, 0, 0, 2, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}