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: 339bfca737a908c196e785a0e8c58ec96a1db96fbfdc95ed34a1202e69201967
Tx prefix hash: ad63b868d9bfacf8bcfa0ef316ce3be488dc1c8c8c70beca4e4757d637786227
Tx public key: 3279b46c9763690c42c8c40d064d33e874f2440ddee171b49d07298fb9e64310
| Timestamp: 1779843299 | Timestamp [UTC]: 2026-05-27 00:54:59 | Age [y:d:h:m:s]: 00:013:00:40:58 |
| Block: 2421 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5465 | RingCT/type: yes/0 |
| Extra: 013279b46c9763690c42c8c40d064d33e874f2440ddee171b49d07298fb9e6431002090000000126697be300 | ||
1 output(s) for total of 35.022342717483 HMNY
| stealth address | amount | amount idx | tag |
| 00: 942185603ce5bd21f9332ae54d72ab28962895c62bc778f7bb4f7b687811c93b | 35.022342717483 | 2843 of 0 | <27> |
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": 2481,
"vin": [ {
"gen": {
"height": 2421
}
}
],
"vout": [ {
"amount": 35022342717483,
"target": {
"tagged_key": {
"key": "942185603ce5bd21f9332ae54d72ab28962895c62bc778f7bb4f7b687811c93b",
"view_tag": "27"
}
}
}
],
"extra": [ 1, 50, 121, 180, 108, 151, 99, 105, 12, 66, 200, 196, 13, 6, 77, 51, 232, 116, 242, 68, 13, 222, 225, 113, 180, 157, 7, 41, 143, 185, 230, 67, 16, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}